Search Issue Tracker
Not Reproducible
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]
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This clearly happened based on the attached files but no-one can reproduce it any more; if it occurs again we'll reopen it.