Search Issue Tracker
Duplicate
Votes
1
Found in
2017.2.0f2
Issue ID
956742
Regression
Yes
If "Box Collider 2D" is disabled inside the Animation window, trying to enable it in the inspector leads to errors/crash
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Open "Level_Apartments" scene
3. In the Hierarchy window expand "Doors" and select all the children "Door" GO
4. Open the Animation window
5. Uncheck "Door : Box Collider 2D.Enabled"
6. In the Inspector window Check the first "Box Collider 2D" box
7. See that there are errors in the Console
8. Enter Play mode
Expected Result: After step 6 no errors should appear/ After step 8 the Editor should enter Play mode
Actual Result: Errors appear after step 6 and after step 8 the Editor crashes ("Unity Editor has stopped working")
Reproduced with: 2017.3.0b4, 2017.3.0b3, 2017.2.0f3, 2017.1.2f1, 2017.1.1p4, 2017.1.1p2
Regression introduced in: 2017.1.1p2
Did not reproduce on: 2017.1.1p1, 2017.1.1f1, 5.6.4f1(Script Errors)
Note:
Crash doesn't always open the Crash Reporter
Error:
"Assertion error: Cannot create Collider2D shapes already exists"
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
This is a duplicate of issue #957044