Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.4.X
Votes
0
Found in
2017.4
2018.4
2019.1
2019.1.6f1
2019.2
2019.3
Issue ID
1174548
Regression
No
LogStringToConsole is performing too many allocations when printing to console which results in calling GC.collect() often
To reproduce:
1. Open attached project "StackTraceBR.zip"
2. Make sure the Profiler window is open and only GarbageCollector graph is enabled in CPU usage section
3. Enter Play mode
Result: LogStringToConsole is allocating ~9 kb of garbage each frame, GC.collect is called every 5-10 seconds
Reproduced in: 2017.4.0f1, 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a11
Note: allocation size does not change if different variable types are printed (ex.: int, string, bool)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment