Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4.0f1
2018.4.13f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1200966
Regression
No
Crash on physx::shdfnd::internal::HashBase when a big amount of GameObjects with Kinematic Rigidbodies are instantiated
Steps to reproduce:
1. Open the attached project ("1200966.zip")
2. Open "SinglePlayer" scene
3. Enter Play mode
4. Wait for a few seconds so all of the GameObjects are instantiated
5. Exit Play mode
Reproduced with: 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Couldn't test with 2017.4 due to console errors
First 4 lines of the stacktrace:
0x00007FF7ADBF0647 (Unity) physx::shdfnd::internal::HashBase
0x00007FF7ADBEC5A2 (Unity) physx::Sc::ElementInteractionMarker::~ElementInteractionMarker
0x00007FF7ADBEC884 (Unity) physx::Sc::ElementInteractionMarker::`vector deleting destructor'
0x00007FF7ADBF011A (Unity) physx::shdfnd::PoolBase
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note:
Too many objects in a tight spot, each overlapping each pairwise. The physics engine creates an interaction object per each overlapping pair, and while there is no clear limit on those, this project has a potential to result with more than 81 million interactions. This is perhaps unintentional and goes a little beyond what can be simulated by the physics engine reliably well.