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
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- "UnityEngine.SystemInfo.processorFrequency" logs a value of 0 on M1 macs
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
Add comment