Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b3
Issue ID
877599
Regression
Yes
Enabling and Disabling Collider2D in the same frame while colliding with other colliders usually results in crash
To reproduce:
1. Open attached project "zombiesNew.zip"
2. Open and Play "Test" scene.
3. Unity will crash.
Reproducible: 5.6.0b4
Not reproducible: 5.4.1f1, 5.5.1f1, 5.6.05b, 2017.1.0a5
Workaround:
wait at least 1 frame before setting Collider2D to enabled, after it was disabled.
It also gives these errors:
Assertion failed on expression: 'contactState == Collision2D::ContactStay'
Assertion failed on expression: 'colliderItr != m_Collisions.end ()'
Assertion failed on expression: 'collision.m_ContactCount >= 0'
Fixed in: 5.6.05b (no errors, no crash)
Comments (2)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
M0rph3v5
Apr 02, 2017 11:55
In my case it's enabling and disabling 'simulated' in one frame btw.
M0rph3v5
Apr 02, 2017 11:51
This is still a problem! In Unity 5.6.0f3.