Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available. Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Unity 6000.2 has reached its end of life and will not receive further updates. If you need additional fixes, please upgrade to a newer Unity version.
A crash in the Unity Editor has been observed, affecting various workflows including:
Reproducible with: 6000.0.34f1 - 6000.0.62f1, 6000.2.0b3 - 6000.2.12f1, 6000.3.0b2 - 6000.3.0b7, 6000.4.0a1 - 6000.4.0a4, 6000.5.0a1
Reproduced on: Windows 10, Windows 11 (users devices)
Not reproduced on: No other environment tested
Note: Not reproduced by CQA
First few lines of the stack trace:
0x00007FFA67A965A6 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\domain.c:1091] mono_domain_jit_foreach
0x00007FFA67A9602F (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\domain.c:1043]
mono_domain_foreach
0x00007FFA67BE4BFB (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\etw-profiler.c:309] Private_EventControlCallback
0x00007FFA67BE3445 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\CLR-ETW-Generated.h:426] McGenControlCallbackV2
Issues you vote on will appear here