Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
0
Found in
Issue ID
1228264
Regression
No
CrashReporting::LogBuffer::RecordLogMessage may crash if called from multiple background threads
If there are many background threads all logging messages at once, CrashReporting::LogBuffer::RecordLogMessage may crash.
As a workaround, setting any of the following to zero will temporarily resolve the issue:
- "Debug.Log Count" in the services window
- https://docs.unity3d.com/ScriptReference/CrashReportHandler.CrashReportHandler-logBufferSize.html or
- https://docs.unity3d.com/ScriptReference/CrashReporting.CrashReportingSettings-logBufferSize.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
- [iOS] The safe area value changes when reopening the app in Landscape orientation
- Light flickering when using Forward+ on Mobile
- Crash on mono_g_hash_table_find_slot when entering Play Mode
- [iOS] Crash when pressing "Done" on the keyboard layout
Add comment