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
- “InvalidOperationException” errors are thrown when entering Play Mode in the Timeline’s Customization Samples
- EditorSceneManager.SaveOpenScenes returns true when the Scene is not successfully saved
- ScrollView snaps back to the target after ScrollTo() when the UI updates every frame
- Dlig ligatures are applied by default when "liga" Font Feature is enabled
- Colliders are rendered deformed when viewed through Physics Debugger in Scene View
Add comment