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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment