Search Issue Tracker
By Design
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.24f1
Issue ID
UUM-85236
Regression
No
The Standalone Profiler shows high CPU Usage
Steps to reproduce:
{}{{}}1. Create a new Unity Project with Universal 3D template
2. In the Editor Menu, select Window -> Analysis -> Profiler (Standalone Process)
3. In the Profiler set Target Selection to "Play Mode"
4. Go back to the Editor and enter the Play Mode
5. Go back to the Profiler window and observe CPU Usage field
Actual results: CPU Usage is 90-200 ms
Expected results: CPU Usage is 5-30 ms
Reproducible with versions: 2021.3.45f1, 2022.3.51f1 6000.0.24f1, 6000.1.0a2
Tested on (OS): macOS Sonoma 14.5 (Intel)
Note:
- Issue is also reproducible with: Universal 2D, High Definition 3D, AR Mobile, 2D Platformer Microgame and 2D (Built-In Render Pipeline) templates
- Issue is not reproducible on non-Standalone Profiler
- Issue is not reproducible when Profiler (Standalone Process) window is unfocused
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
This is because the URP Sample does not have "run in background" ticked in the Player Project Settings (see the related comment for a screenshot with the option in).
With that option unticked, when the standalone profiler is the foreground app the Editor will stop running the game and the framerate shown will be lower.
If you tick that checkbox then the sample updates properly when the standalone profiler is in the foreground and the framerate should be higher again.