Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2021.2
2021.2.2f1
2021.3
2022.1
2022.2
Issue ID
1419807
Regression
No
Crash on mono_log_write_logfile when calling a specific method
Reproduction steps:
1. Open the user's attached project
2. Add the "Assets/Units/DELETEME.cs" script to any GameObject in the scene
3. Enter Play Mode
Expected result: Editor enters Play Mode successfully
Actual result: Editor crashes
Reproducible with: 2021.2.19f1, 2021.3.1f1, 2022.1.0f1, 2022.2.0a8
Not reproducible with: 2022.2.0a9, 2022.2.0a11
Could not test with: 2019.4.38f1, 2020.3.34f1 (Script syntax errors)
First lines of stacktrace:
0x00007FFD71B44F69 (KERNELBASE) RaiseException
0x00007FFCDB7B064C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FFCDB79C4A2 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FFCDB79C57C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:215] monoeg_assertion_message
0x00007FFCDB814562 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\class-setup-vtable.c:1710] mono_class_setup_vtable_general
0x00007FFCDB8115D0 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\class-setup-vtable.c:899] mono_class_setup_vtable_full
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a9