Mysterious Crashes in Editor and Builds

My team and I recently upgraded from 2017.1 to 2018.3 and the game started crashing often.
We even got some kind of reproduceability where we can know it’s going to crash after some steps, but there is no specific trigger.
The closest thing to an “answer” I’ve found is a stack trace out of an editor crash:
========== OUTPUTTING STACK TRACE ==================

0x0000000140B3ACC3 (Unity) PhysicsManager::Simulate
0x0000000140B33666 (Unity) PhysicsManager::InitializeClass'::2’::FixedUpdatePhysicsFixedUpdateRegistrator::Forward
0x000000014095B397 (Unity) ExecutePlayerLoop
0x000000014095B463 (Unity) ExecutePlayerLoop
0x000000014095E721 (Unity) PlayerLoop
0x000000014133DE2F (Unity) PlayerLoopController::UpdateScene
0x000000014133C3E0 (Unity) Application::TickTimer
0x000000014149881B (Unity) MainMessageLoop
0x000000014149A4B6 (Unity) WinMain
0x00000001424864EA (Unity) __scrt_common_main_seh
0x00007FFF73C24034 (KERNEL32) BaseThreadInitThunk
0x00007FFF74FA3691 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

Any ideas?

4546486–421900–Crash_2019-05-16_043609859.zip (296 KB)

2 Likes

Experiencing the same crash in one of my projects in 2019.1.4f1

Seems to happen only when objects with rigidbodies that have had some kind of force applied to them get disabled or destroyed. Seems like the physics engine is still trying to access these objects on the frame after they are destroyed for some reason.

I filed a bug report which I got a response from @evelinastaniulyte redirecting me to an existing bug report that says it has been fixed in 2019.3. I replied to the email asking if we can expect this same fix to also be rolled out to earlier 2019.x versions (2019.1 and 2019.2 since they both have the problem as well) and have not received a confirmation.

Awaiting more info, would really like to get an update on this as we don’t feel comfortable upgrading the project to 2019.3 since it has not been released yet, but this issue is 100% reproducible in our game. And the only way to prevent the crash for us, is to not ever apply physics to our rigidbodies, which obviously is a pretty major road block.

Right after replying here, I went and checked that issue on the issue tracker and they have updated the status

Looks like we WILL be getting a fix for 2019.2 soon

Hi,

I am still having this crash on Unity 2019.2.5f1.

Still getting:
========== OUTPUTTING STACK TRACE ==================
0x0000000140B485D3 (Unity) PhysicsManager::Simulate
0x0000000140B40F76 (Unity) PhysicsManager::InitializeClass'::2’::FixedUpdatePhysicsFixedUpdateRegistrator::Forward
0x0000000140968A07 (Unity) ExecutePlayerLoop
0x0000000140968AD3 (Unity) ExecutePlayerLoop
0x000000014096BD91 (Unity) PlayerLoop
0x0000000141355A2F (Unity) PlayerLoopController::UpdateScene
0x0000000141353A00 (Unity) Application::TickTimer
0x00000001414B0F13 (Unity) MainMessageLoop
0x00000001414B2BFD (Unity) WinMain
0x00000001424AEE6A (Unity) __scrt_common_main_seh
0x00007FF8E2067BD4 (KERNEL32) BaseThreadInitThunk
0x00007FF8E2DCCED1 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========

in 2018.4.1.

edit: Apparently fixed in 2020 and its working its way into 2018.4 since august

edit2: Though the issue 1122684 is fixed in 2018.4.8 release notes…

Hello,

Sorry to bump this up, but we have similar issue. Any advice what might be the cause? It’s happening only in builds and not in editor.

0x00007FFABBF4A2CD (UnityPlayer) physx::NpScene::simulateOrCollide
0x00007FFABBF4A0CE (UnityPlayer) physx::NpScene::simulate
0x00007FFABAD5A849 (UnityPlayer) PhysicsManager::Simulate
0x00007FFABAD56894 (UnityPlayer) `PhysicsManager::InitializeClass'::`2'::FixedUpdatePhysicsFixedUpdateRegistrator::Forward
0x00007FFABB5F2E6E (UnityPlayer) ExecutePlayerLoop
0x00007FFABB5F2F3F (UnityPlayer) ExecutePlayerLoop
0x00007FFABB5F5EE0 (UnityPlayer) PlayerLoop
0x00007FFABB066852 (UnityPlayer) PerformMainLoop
0x00007FFABB064B7A (UnityPlayer) MainMessageLoop
0x00007FFABB06994D (UnityPlayer) UnityMainImpl
0x00007FFABB06BD6B (UnityPlayer) UnityMain
0x00007FF6747411FA (The Universim) __scrt_common_main_seh
0x00007FFB1FDD7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFB1FF2CED1 (ntdll) RtlUserThreadStart

Happening in 2018.4.12f1

Thanks.

I believe this is causing crashes in 2019.0f5 still…worse than 2019.of3. I thought just maybe that would fix it…but more issues more frequently.

I have this problem on 2019.3.10f1, but it only happens in editor, bulid always works good.