Search Unity

PhysX crash: ::findTriggerContacts

Discussion in 'Physics' started by Alabatross, Aug 22, 2016.

  1. Alabatross

    Alabatross

    Joined:
    Dec 15, 2012
    Posts:
    223
    I'm currently dealing with a crash and I am having trouble pinpointing it since this is a rather large project. I was hoping a Unity developer could maybe gather some information from the stack trace about what it has to do with so I can have better luck figuring it out?


    Here is a build crash:
    Code (csharp):
    1.  
    2. ========== OUTPUTING STACK TRACE ==================
    3.  
    4. 0x00E683F0 (VBuild1012) [c:\buildslave\physx\build\source\simulationcontroller\src\scnphasecore.cpp:1588] physx::Sc::NPhaseCore::findTriggerContacts
    5. 0x00E687E9 (VBuild1012) [c:\buildslave\physx\build\source\simulationcontroller\src\scnphasecore.cpp:1508] physx::Sc::NPhaseCore::narrowPhase
    6. 0x00DACE44 (VBuild1012) [c:\buildslave\physx\build\source\simulationcontroller\src\scscene.cpp:1349] physx::Sc::Scene::postIslandGen
    7. 0x00DB4D0C (VBuild1012) [c:\buildslave\physx\build\source\common\src\cmtask.h:96] physx::Cm::DelegateTask<physx::Sc::Scene,&physx::Sc::Scene::postIslandGen>::runInternal
    8. 0x00865496 (VBuild1012) [c:\buildslave\unity\build\runtime\dynamics\physicsmanager.cpp:364] PhysxJobFunc
    9. 0x004E72FB (VBuild1012) [c:\buildslave\unity\build\runtime\jobs\internal\jobqueue.cpp:345] JobQueue::Exec
    10. 0x004E7A95 (VBuild1012) [c:\buildslave\unity\build\runtime\jobs\internal\jobqueue.cpp:597] JobQueue::ExecuteOneJob
    11. 0x006666F9 (VBuild1012) [c:\buildslave\unity\build\runtime\misc\player.cpp:1665] PlayerLoop
    12. 0x007602D7 (VBuild1012) [c:\buildslave\unity\build\platformdependent\winplayer\winmain.cpp:551] MainMessageLoop
    13. 0x00762584 (VBuild1012) [c:\buildslave\unity\build\platformdependent\winplayer\winmain.cpp:974] PlayerWinMain
    14. 0x00BA5D58 (VBuild1012) [c:\buildslave\unity\build\platformdependent\winplayer\shimmain.cpp:6] WinMain
    15. 0x00BDBCC8 (VBuild1012) [f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c:275] __tmainCRTStartup
    16. 0x7586337A (kernel32) BaseThreadInitThunk
    17. 0x77BF9882 (ntdll) RtlInitializeExceptionChain
    18.  
    19. ========== END OF STACKTRACE ===========
    20.  

    Here is the editor crash:

    (For some reason this one was longer this time)

    Code (csharp):
    1.  
    2. ========== OUTPUTING STACK TRACE ==================
    3.  
    4. 0x0000000141B57D53 (Unity) physx::Gu::gjkRelative<physx::Gu::BoxV,physx::Gu::ConvexHullV>
    5. 0x0000000141B6CEEA (Unity) physx::Gu::gjkRelativeTesselation<physx::Gu::BoxV,physx::Gu::ConvexHullV>
    6. 0x0000000141B6C807 (Unity) physx::Gu::GJKRelativeTesselation
    7. 0x0000000141B03AD9 (Unity) physx::Gu::intersectBoxConvex
    8. 0x0000000141B05D49 (Unity) physx::Gu::checkOverlapCapsule_convexGeom
    9. 0x0000000141BEAFA7 (Unity) physx::Sc::NPhaseCore::findTriggerContacts
    10. 0x0000000141BEB3D1 (Unity) physx::Sc::NPhaseCore::narrowPhase
    11. 0x0000000141B2087C (Unity) physx::Sc::Scene::postIslandGen
    12. 0x0000000141B1F172 (Unity) physx::Cm::BaseTask::run
    13. 0x0000000140F321C7 (Unity) NovodexAllocator::deallocate
    14. 0x0000000140171219 (Unity) JobQueue::Exec
    15. 0x0000000140171399 (Unity) JobQueue::ExecuteJobFromHighPriorityStack
    16. 0x0000000140171EBE (Unity) JobQueue::ExecuteOneJob
    17. 0x0000000140F3C31C (Unity) PhysicsManager::FixedUpdate
    18. 0x00000001403B83DE (Unity) PlayerLoop
    19. 0x0000000140B9762C (Unity) Application::UpdateScene
    20. 0x0000000140B990E9 (Unity) Application::UpdateSceneIfNeeded
    21. 0x0000000140B9F63C (Unity) Application::TickTimer
    22. 0x0000000140DCFD37 (Unity) RelaunchUnity
    23. 0x0000000140DD131B (Unity) WinMain
    24. 0x000000014151EF94 (Unity) read
    25. 0x0000000077AC5A4D (kernel32) BaseThreadInitThunk
    26.  
    27. ========== END OF STACKTRACE ===========
    28.  
     
  2. Superjayjay

    Superjayjay

    Joined:
    Mar 28, 2013
    Posts:
    69
    Sorry to necro an old thread but I'm having the same exact issue. Did you find a solution? It's still happening in 5.4.4 and it's driving me mad.