Search Issue Tracker
Third Party Issue
Votes
0
Found in
2021.3.38f1
2022.3.30f1
6000.0.4f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-72595
Regression
No
Editor crashes on physx::shdfnd::internal::HashBase or freezes when instantiating a lot of GameObjects
Reproduction steps:
1. Open the “user’s attached project”
2. Open the “MIRROR” scene
3. Enter Play Mode
4. Observe the Editor crash or freeze
Reproducible with versions: 2021.3.38f1, 2022.3.30f1, 6000.0.4f1
Reproducible on: macOS Sonoma 14.4.1 (Intel), Windows 11 (By the reporter)
Not reproducible on: no other environment tested
Notes:
- The issue is caused by the MazeAttempt.cs script that Instantiates a lot of GameObject. The crash or freeze does not occur after disabling it.
- Also reproducible in Player
First few lines of StackTrace:
{noformat}#0 0x0000010b7cb3cf in physx::shdfnd::internal::HashBase<physx::Bp::Pair, physx::Bp::Pair, physx::shdfnd::Hash<physx::Bp::Pair>, physx::shdfnd::internal::HashSetBase<physx::Bp::Pair, physx::shdfnd::Hash<physx::Bp::Pair>, physx::shdfnd::NonTrackingAllocator, false>::GetKey, physx::shdfnd::NonTrackingAllocator, false>::reserveInternal(unsigned int)
#1 0x0000010b7c271d in physx::Bp::AABBManager::postBpStage3(physx::PxBaseTask)
#2 0x0000010b7263d1 in physx::Cm::Task::run()
#3 0x0000010929bcc9 in PhysicsCommands::Physx::Simulate(void, PhysicsCommands::Command&)
#4 0x0000010929fc6a in PhysicsScene::Simulate(float){noformat}
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
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
Resolution Note:
This issue is tied to the internal of PhysX where instantiating a very large number of bodies with lots of shapes w/o simulating in between can cause the internal tracking structures to fail. We'll migrate this case to an internal ticket and see what can be done about it.
Cheers,
AlexRvn.