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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment