Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
901465
Regression
Yes
CollisionListener2D::ProcessContacts crashes when unparenting game objects and destroying their parent which has Rigidbody2D
CollisionListener2D::ProcessContacts crashes in Play mode when unparenting game objects and destroying their parent which has Rigidbody2D
To reproduce:
1. Download attached project "901465.zip" and open in Unity
2. Press "Play" button
3. Walk on the "Boomer" game object
4. Wait few seconds until "Boomer" game object explodes
Expected result: After "Boomer" game object explodes, "Player(Clone)" game object explodes too.
Actual result: After "Boomer" game object explodes, Unity crashes
Note: If you delete Rigidbody2D from "Player(Clone)" game object, which is created when you press "Play" button and in Scene view put "Boomer" game object on "Player(Clone)" game object, then when "Boomer" game object explodes, no crash occurs (Works on Unity 5.6.0b5 or newer). If you build game on Windows, it also crashes
Reproduced on Unity 5.6.0p2 and 2017.1.0b1
Not reproduced on Unity 5.5.3p1
Regression on Unity 5.6.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Element name field has no character limit in UI Builder
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Add comment