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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment