Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1132126
Regression
No
Unity crashes after a deactivated child with rigidbody is unparented, its parent deleted, the child activated and collided
How to reproduce:
1. Open attached project "RigidBodyCrash.zip" and scene "HardCrash"
2. Enter Play mode
3. Unparent child called "Children", a child of "Parent Cube" object
4. Delete "Parent Cube" object from the Hierarchy window
5. In Hierarchy window, select "Children" object and in Inspector window make it active
6. Observe the falling balls in Game or Scene views
Expected result: the balls collide with the ground
Actual result: when the balls collide with the ground Unity crashes
Reproducible with: 2017.4.22f1, 2018.3.7f1, 2019.1.0b5, 2019.2.0a6
Could not test with: 2019.2.0a7 due to gravity not working correctly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[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
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment