Search Issue Tracker

Fixed

Fixed in 6000.0.2f1

Votes

0

Found in

6000.0.1f1

Issue ID

UUM-71934

Regression

No

Crash on mono_log_write_logfile when opening a specific project

--

-

Reproduction steps:
1. Open the attached “Jump” project
2. Observe the Editor

Expected result: The Editor does not crash
Actual result: The Editor crashes

Reproducible with: 6000.0.1f1
Fixed in: 6000.0.2f1
Could not test with: 2021.3.38f1 (Could not downgrade the project due to multiple package dependencies), 2022.3.28f1 (“error CS0104” compilation errors in the user’s script)

Reproducible on: MacOS Sonoma 14.4.1 (Intel), Windows 11 (user’s)
Not reproducible on: No other environment tested

Notes:
- In MacOS Editor, “mono_os_mutex_lock: pthread_mutex_lock failed with "Invalid argument" (22)" is logged before the crash

First few lines of the stack trace (Windows):

{noformat}0x00007FFB305E0C1C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FFB305CC822 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FFB305CC8FC (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:217] monoeg_assertion_message
0x00007FFB305E0D5C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-internal-hash.c:49] mono_internal_hash_table_lookup
0x00007FFB30634E1D (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\class-init.c:455] mono_class_create_from_typedef {noformat}

First few lines of the stack trace (MacOS):

{noformat}#0 0x007ff8060c814a in __pthread_kill
#1 0x007ff806026a39 in abort
#2 0x000001676c4de5 in monoeg_g_printv
#3 0x000001676ab5a1 in mono_log_write_logfile
#4 0x000001676c5147 in monoeg_g_logv_nofree{noformat}

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.