Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.1.0b3
Issue ID
907157
Regression
No
[STW2017.1] Crashed at Collider2D_Get_Custom_PropComposite when clicking on UI elements in the Editor
Steps to reproduce:
1. Create a project
2. Add a Sprite in the Hierarchy
3. Add a BoxCollider2D to the Sprite
4. Add a RigidBody2D to the Sprite
5. Add a CompositeCollider2D to the Sprite
6. Play a Scene
7. Stop playing a Scene
8. Remove CompositeCollider2D from the Sprite
9. Observe the error in the Console window:
Assertion failed: Assertion failed on expression: 'm_InstanceID != InstanceID_None'
10. Start clicking on UI elements in the Editor (until Editor will crash)
11. Observe the crash
Expected result: Unity should not crash
Actual result: Unity crashes
Reproduced with: 5.6.0p4, 2017.1.0b3, 2017.1.0b4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment