Search Issue Tracker
Fixed in 2017.1.X
Votes
1
Found in
5.5.0f3
Issue ID
891305
Regression
No
Unity crashes in <tessMeshAddEdgeVertex>, when 2D colliders collide
Reproduction steps:
1. Open the attached file "case_891305_smallProject.zip";
2. Open the scene "DevTest";
3. Enter Play mode;
Actual result: Unity crashes in <tessMeshAddEdgeVertex>.
Expected result: Unity should not crash.
Note: there is a conflict between 2D colliders. When the Box Collider 2D is turned off of the object "placeholderPlayer", Unity does not crash. Or if the collider is turned off of the prefab "ownage", Unity does not crash. Also, when Freeze Rotation Z is disabled of the prefab "ownage", Unity does not crash.
Reproduced with: 5.3.7p4, 5.4.5f1, 5.5.0a6, 5.5.2p3, 5.6.0f1, 2017.1.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Add comment