Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

[CRASH] PhysX crashes in 5.5.3

Discussion in 'Physics' started by CradleGamesStudio, Apr 10, 2017.

  1. CradleGamesStudio

    CradleGamesStudio

    Joined:
    Jan 23, 2017
    Posts:
    5
    Code (CSharp):
    1.  
    2. ========== OUTPUTING STACK TRACE ==================
    3.  
    4. 0x00007FF75C5CD756 (Hellpoint_Demo) physx::shdfnd::Time::getCurrentTimeInTensOfNanoSeconds
    5. 0x00007FF75C5CDD2D (Hellpoint_Demo) physx::shdfnd::Time::getCurrentTimeInTensOfNanoSeconds
    6. 0x00007FF75C5CE4A8 (Hellpoint_Demo) physx::shdfnd::Time::getCurrentTimeInTensOfNanoSeconds
    7. 0x00007FF75C4DA8B2 (Hellpoint_Demo) physx::shdfnd::Foundation::getNamedAllocMap
    8. 0x00007FF75BE130DF (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    9. 0x00007FF75BB7E966 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    10. 0x00007FF75BB7EBA4 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    11. 0x00007FF75BB7EC3B (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    12. 0x00007FF75BC3C698 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    13. 0x00007FFB7DF88364 (KERNEL32) BaseThreadInitThunk
    14. 0x00007FFB801E70D1 (ntdll) RtlUserThreadStart
    15.  
    16. ========== END OF STACKTRACE ===========
    17.  
    Code (CSharp):
    1.  
    2. ========== OUTPUTING STACK TRACE ==================
    3.  
    4. 0x00007FFB5A101DAD (mono) mono_set_defaults
    5. 0x00007FF75BBA7070 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    6. 0x00007FF75BBE2CB2 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    7. 0x00007FF75BBE2627 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    8. 0x00007FF75BBE28ED (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    9. 0x00007FF75BBAA88D (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    10. 0x00007FF75C176387 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    11. 0x00007FF75C17655A (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    12. 0x00007FF75C17A0B8 (Hellpoint_Demo) physx::shdfnd::Foundation::getErrorMutex
    13. 0x00007FF75C2809B0 (Hellpoint_Demo) physx::shdfnd::Foundation::getAllocator
    14. 0x00007FFB7DF88364 (KERNEL32) BaseThreadInitThunk
    15. 0x00007FFB801E70D1 (ntdll) RtlUserThreadStart
    16.  
    17. ========== END OF STACKTRACE ===========
    18.  
    PhysX in 5.5.3 appears to be highly unstable lately.
     
    CradleGamesStudio, Apr 10, 2017
    #1

  2. Edy

    Edy

    Joined:
    Jun 3, 2010
    Posts:
    2,430
    I'm currently on 5.5.2f1 and physics seems rather stable, if that helps.
     
    Edy, Apr 19, 2017
    #2

  3. Deznom

    Deznom

    Joined:
    Oct 7, 2015
    Posts:
    15
    Crash like this can happen if you are deleting rigidbodies without syncing with physics update.
     
    Deznom, May 3, 2017
    #3

  4. Fuegan

    Fuegan

    Joined:
    Dec 5, 2012
    Posts:
    20
    I'm not sure what exactly do you mean by that. Could you be more specific because I'm not sure how are you supposed to sync with physics update?

    Like let say I have a GameObject GO wich have a rigidbody, when or how can I destroy it safely?
     
    Fuegan, May 18, 2017
    #4