Search Issue Tracker
Fixed
Fixed in 6000.4.0a3
Votes
0
Found in
2021.3.32f1
2022.3.14f1
2023.2.1f1
2023.3.0a15
Issue ID
UUM-57941
Regression
No
GC.Collect process takes more time than specified garbage collection duration
Reproduction steps:
1. Open the attached “BugReport“ project
2. Open the Profiler window (Window > Sequencing > Timeline)
3. Build the Player (File > Build And Run)
4. After the building process is finished, let the Profiler record for a few seconds and then pause it
5. In the Profiler’s Hierarchy window search bar, enter “GC.Collect“
6. Select a frame from the Profiler’s CPU Usage module and then go forward one frame at a time, until a “GC.Collect” process appears in the Profiler’s Hierarchy window
7. Observe the “GC.Collect” process’s “Time ms”
Expected results: “Time ms“ should not exceed 1ms, because garbage collection duration is specified 1ms
Actual results: “Time ms“ exceeds the specified garbage collection duration
Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a15
Reproducible on: Windows 11, MacOS Ventura 13.3 (Intel)
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6000.4.0a3):
GarbageCollector.incrementalTimeSliceNanoseconds docs updated, by clarifying regrading time slice limit.