Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.0f3
Issue ID
845043
Regression
Yes
g_logv crash caused by Charon.exe and Mono Develop with attached debugger
Repro steps:
1. Open "unity_monodevelop_crush.zip"
2. Open gamedata.jsn (Assets>StreamingAssets>gamedata)
3. Open Mono Develop
4. Reimport all assets in Unity (Editor hangs)
5. In Mono Develop attach debugger to Unity process and press "Pause" multiples times
6. In windows Task Manager kill "Charon.exe" process
Stack trace:
g_logv
g_log
Actual: Crash caused by Charon.exe and Mono Develop with attached debugger
Expected: Crash should not occur
Reproduced on: 5.3.7f1, 5.4.0f3, 5.5.0b11
Did not reproduce on: 5.2.4f1 (only Mono Develop hangs once you kill Charon.exe works fine)
Regression begins with 5.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment