Search Issue Tracker
By Design
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
Issue ID
UUM-109538
Regression
No
Crash on mono_jit_compile_method_with_opt when opening a specific project
How to reproduce:
1. Open the attached “CrashRepro“ project
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
Note: Issue is only reproducible when opening the project first time, when opening it the second time, the “Corrupted Library Detected“ pop-up is shown and if the Library is rebuilt, the project will open
First few lines of the stack trace:
0x00007ffdb16427db (mono-2.0-bdwgc) mono_jit_compile_method_with_opt (at C:/build/output/Unity-Technologies/mono/mono/mini/mini-runtime.c:2605)
0x00007ffdb1642217 (mono-2.0-bdwgc) compile_special (at C:/build/output/Unity-Technologies/mono/mono/mini/mini-runtime.c:2432)
0x00007ffdb16426b1 (mono-2.0-bdwgc) mono_jit_compile_method_with_opt (at C:/build/output/Unity-Technologies/mono/mono/mini/mini-runtime.c:2666)
0x00007ffdb173cd84 (mono-2.0-bdwgc) common_call_trampoline (at C:/build/output/Unity-Technologies/mono/mono/mini/mini-trampolines.c:641)
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note:
This is unfortunately not an something we can fix as it's due to a data corruption. The "Corrupted Database" warning is correct and is the only solution.
If this issue re-appears or you find a way to trigger the corruption we would be happy to take another look at the issue.