Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.62f1
6000.2.12f1
6000.3.0b7
6000.4.0a4
6000.5.0a1
Issue ID
UUM-126856
Regression
No
Crash on mono_domain_jit_foreach when performing various actions in the Editor
A crash in the Unity Editor has been observed, affecting various workflows including:
- Entering Play mode
- Using a script to change scenes while in Play mode
- Editing a shader
- Sitting idle
- Altering or adding components to a GameObject
- Dragging and dropping a script into the Assets folder
- Duplicating scenes
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
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note:
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.
Resolution Note (6000.5.X):
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.