Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
8
Found in
2018.3.0f2
Issue ID
1113545
Regression
No
Crash on SimulationCallbackReceiver::onContact when objects are destructing
How to reproduce:
1. Open attached Unity project
2. Enter the Play moe
3. Move player
-- Editor will crash on SimulationCallbackReceiver::onContact after few seconds
Reproduced with: 2019.1.0a13, 2018.3.1f1
Note: Can't test on 2018.2 and 2017.4 because of errors.
Stacktrace:
0x00007FF706CE6D1C (Unity) SimulationCallbackReceiver::onContact
0x00007FF7079BFAB4 (Unity) physx::Sc::Scene::fireQueuedContactCallbacks
0x00007FF707961567 (Unity) physx::NpScene::fetchResults
0x00007FF706A4AA4C (Unity) PhysicsManager::Simulate
0x00007FF706A4637E (Unity) `PhysicsManager::InitializeClass'::`2'::FixedUpdatePhysicsFixedUpdateRegistrator::Forward
0x00007FF706626EA8 (Unity) ExecutePlayerLoop
0x00007FF706626F86 (Unity) ExecutePlayerLoop
0x00007FF70662BBE0 (Unity) PlayerLoop
0x00007FF705363390 (Unity) PlayerLoopController::UpdateScene
0x00007FF705360418 (Unity) Application::TickTimer
0x00007FF70561E843 (Unity) MainMessageLoop
0x00007FF7056281E7 (Unity) WinMain
0x00007FF707F2D40E (Unity) __scrt_common_main_seh
0x00007FFE2ECF3034 (KERNEL32) BaseThreadInitThunk
0x00007FFE31583691 (ntdll) RtlUserThreadStart
Fixed in: 2019.3.0a2.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
hww
Mar 14, 2019 14:54
We see perhaps the same problem with our application, using Unity 2018.3.8. The exception thread stack trace looks like this:
Thread 1 (Thread 0x7f57d3ef6b80 (LWP 8085)):
#0 0x00007f57d2dcaeb0 in waitpid () from /lib64/libpthread.so.0
#1 0x00007f57b1ef2323 in ?? () from /space/crane/crane-20190312/crane-20190312_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#2 <signal handler called>
#3 0x00007f57d2a3f860 in raise () from /lib64/libc.so.6
#4 0x00007f57d2a4142f in abort () from /lib64/libc.so.6
#5 0x000000000156f7f6 in HandleSignal ()
#6 0x00007f57b1f6b8e2 in ?? () from /space/crane/crane-20190312/crane-20190312_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#7 0x00007f57b1e78ecc in ?? () from /space/crane/crane-20190312/crane-20190312_Data/MonoBleedingEdge/x86_64/libmonobdwgc-2.0.so
#8 <signal handler called>
#9 0x0000000000000000 in ?? ()
#10 0x0000000000953fb3 in onContact ()
#11 0x0000000001ffc8f2 in physx::Sc::Scene::fireQueuedContactCallbacks (this=this@entry=0x73c3470, asPartOfFlush=asPartOfFlush@entry=false) at ./PhysX/Source/SimulationController/src/ScScene.cpp:4501
#12 0x0000000001fa44ae in physx::Scb::Scene::fireQueuedContactCallbacks (this=0x73c3460) at PhysX/Source/PhysX/src/buffering/ScbScene.h:265
#13 physx::NpScene::fetchResults (this=0x73c3450, block=<optimized out>, errorState=0x0) at ./PhysX/Source/PhysX/src/NpScene.cpp:2334
#14 0x0000000000912416 in PhysicsManager::Simulate ()
#15 0x0000000000912975 in Forward ()
#16 0x00000000012fb862 in ExecutePlayerLoop ()
#17 0x00000000012fb958 in ExecutePlayerLoop ()
#18 0x0000000001301915 in PlayerLoop ()
#19 0x00000000004d9c1f in main ()