Search Issue Tracker
In Progress
In Progress in 6000.6.X
Votes
0
Found in
6000.0.75f1
6000.3.16f1
6000.4.8f1
6000.5.0b9
6000.6.0a5
Issue ID
UUM-142773
Regression
No
Crash on mono_log_write_logfile when more than one copy of bee_backend is running
How to reproduce:
- Create a new URP project
- In the Player settings, change the Active Input Handling setting to any other option
- In the following prompt about restarting the Editor, select "accept"
- When the Editor loading window appears, close it by clicking x at the top right corner of the window
- Open the Windows task manager and type "bee" in the search bar
- Launch the project again and let the project compile for some time until bee initializes it's cache (visible in the task manager)
- Close the Editor loading window by clicking x at the top right corner of the window
- Quickly launch the project again
- Observe the frozen Editor loading screen
Reproducible with versions: 6000.0.0f1, 6000.0.75f1, 6000.3.16f1, 6000.4.8f1, 6000.5.0b9, 6000.6.0a5
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Workaround: Close the bee_backend.exe process from the task manager before opening the project
Notes:
- Reproducing this issue might take a couple of attempts, it is very dependent on the timing of when you kill the Editor loading process. If you notice that the Editor loading bar has gotten past Running Backend -> Repeat steps 6 - 9
- If the Editor loading window is closed quickly after the freeze happens, no crash occurs and instead the Editor loading process is not killed (visible in the task manager)
- Error always visible in the Editor.log:
ExitCode: 2 Duration: 0s155ms
bee_backend: error: More than one copy of bee_backend running in A:\Unity Projects\My project – PID 27532 waiting
First few lines of StackTrace:
0x00007FFA127FFE0A (KERNELBASE) RaiseException
0x00007FF94B22120C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FF94B20CE12 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FF94B20CEEC (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:217] monoeg_assertion_message
0x00007FF94B376BB6 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\object.c:2303] mono_class_create_runtime_vtable
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on Scripting::ScriptingWrapperFor when exiting Play Mode during an active web request
- Material Inspector shortly disappears resulting in "Add Component" button jumping when the Material is recompiled
- Hand Interaction Profile breaks hand teleport to arbitrary locations
- Grabbing Dynamic Attach interactable in Interaction Simulator makes controller spin
- XRI Starter Assets Interactable shader generates Console warnings
Add comment