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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment