Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b9
6000.5.0a8
6000.6.0a1
Issue ID
UUM-137881
Regression
No
1 KB or more of GC is allocated when Debug logging
How to reproduce:
1. Open the "DebugGCAlloc.zip" project
2. Open the “SampleScene“
3. Open the Window → Analysis → Profiler window
4. Enter Play Mode
5. Click anywhere on the CPU Usage strip in the Profiler
6. Observe the GC column in the Hierarchy tab in the Profiler
Actual result: 1 KB of GC is allocated on 'DebugLog.Update'
Expected result: less or no bytes are allocated on 'DebugLog.Update'
Reproducible in: 2023.1.0a1, 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Note: LogException allocates 6.6 KB, while Log, LogAssertion, LogError, LogWarning allocate 1.0 KB on each call
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment