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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Add comment