Search Issue Tracker
Fixed
Fixed in 2022.3.23f1, 2023.2.16f1, 2023.3.0b5
Votes
1
Found in
2021.3.31f1
2022.3.11f1
2023.1.18f1
Issue ID
UUM-54007
Regression
No
Crash on physx::PxsCCDContext::updateCCD when ContinuousDynamic collision detection is used
How to reproduce:
1. Open the “Memory_Bug“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Press space on the keyboard around 5 times
Expected result: The Editor continues to run
Actual result: The Editor crashes
Reproducible with: 2021.3.31f1, 2022.3.11f1, 2023.1.18f1
Could not test with: 2023.2.0b15, 2023.3.0a11 (due to errors)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
The first few lines of the Stack trace:
0x00007FF7B34A2EB0 (Unity) physx::PxsCCDContext::updateCCD
0x00007FF7B33E2769 (Unity) physx::Sc::Scene::updateCCDSinglePassStage3
0x00007FF7B33DF4D2 (Unity) physx::Cm::BaseTask::run
0x00007FF7B179F8F2 (Unity) MultithreadedJobDispatcher::PhysxJobFunc
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
- Bad performance when executing the Physics.IgnoreCollisions() method while in Play Mode
- Sprite Editor has a thicker separator between buttons when "Sprite Editor" option is selected
- "NullReferenceException: Object reference not set to an instance of an object" error is thrown when UpdateVolumeStack function is called
- [Windows] Unicode custom text input window shows question marks when inserting an emoji
- Memory leak when the VFX Graph Editor is open
Mithra
Mar 20, 2024 05:12
Also happening for ContinuousSpeculative mode.