Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.1f1
Issue ID
1049917
Regression
No
[.NET 3.5] Unity crashes when exiting Play Mode while a GameObject is being destroyed and a Coroutine is being yielded
Repro steps:
1. Open QA attached project "repro"
2. Open Scene "0"
3. Enter Play Mode
4. Press space on your keyboard
5. Exit Play Mode immediately
6. Repeat steps 3-5 until the Editor crashes
Expected: Unity exits Play Mode with no errors
Actual: Errors are thrown and Unity crashes
Reproducible with: 2017.1.4p2, 2017.2.3p2, 2017.4.7f1
Not reproducible with: 2018.1.9f1, 2018.2.0f2, 2018.3.0a4
Notes: Doesn't repro on .NET 4.x
Thrown errors:
Assertion failed: Assertion failed on expression: 'coroutine->m_RefCount > 0'
Assertion failed: Assertion failed on expression: 'coroutine->m_CoroutineEnumeratorGCHandle.HasTarget()'
Assertion failed: Assertion failed on expression: 'coroutine->m_RefCount <= 1000000'
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
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.