Search Issue Tracker
Active
Votes
0
Found in
6000.3.0b7
Issue ID
UUM-125481
Regression
No
Capture List - Blocking IO in the main loop, in development players
Feedback from Val Knight
Hey folks - I was using 6.3 beta at the weekend for a hobby project, and seeing really bad stutters due to the new profiler screenshot functionality.
On a fairly regular interval, I’m getting stalls (hundreds of ms) in profiler metadata tied to screenshots. I’ve just taken a look on trunk, and it appears we’re doing blocking IO in the main loop, in development players.
This seems somewhat bad, as all the profiler data is now going to get incredibly noisy (e.g. my team won’t be able to trust some of the analysis done by Profiler Analyzer, which we use on a somewhat regular basis) and there doesn’t seem to be a way to turn off this new functionality.
!image-2025-10-30-17-07-46-158.png|thumbnail!
!image-2025-10-30-17-08-25-464.png|thumbnail!
[^Instruments Trace - FrameMetadata Stall.trace.zip]
[^Unity Capture.zip]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Add comment