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
- Render Graph Execution errors when using GPU occlusion culling with 'Opaque Objects' frame setting disabled on a Camera
- Animator window: “Delete” menu item not greyed out for Base Layer context menu
- Resetting “PC_RP Asset (Universal Render Pipeline Asset)” causes Game view to become black and throws Renderer and NullReference errors in the Console window
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
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.