Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b1
Issue ID
866831
Regression
Yes
Destroying Rigidbody2D of a colliding object crashes Unity in Rigidbody2D::IsSleeping()
Destroying Rigidbody2D of an object while it is colliding crashes Unity.
Steps to reproduce:
1) Open the attached project.
2) Open 'Test' scene.
3) Enter play mode.
- As soon as the the two squares in the scene touch, Unity will most likely crash, if it doesn't, wait for a few seconds, or:
4) Click on the BottomSquare object in the Hierarchy.
The scene consists of two 2D squares. The bottom one is Kinematic (can be Dynamic and constrained instead, doesn't matter) ant the top one is dynamic. When the scene is played, the top square falls on the bottom one. When they touch, Destroy() method is called on bottom square's Rigidbody2D. This results in a crash in Rigidbody2D::IsSleeping()
Reproduced on:
5.6.0b3, 5.6.0b1, 5.6.0a6, 5.6.0a4
Did not reproduce:
5.6.0a3, 5.5.0p3, 5.4.4f1, 5.3.7p3, 5.2.4f1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
FrankvHoof
Jun 07, 2018 12:54
Issue has returned in Unity 2017.3.0p4