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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Add comment