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
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
- "Pos X" and "Pos Y" are grayed-out in Inspector under Rect Transform when undoing parenting action of LayoutGroup
Add comment