Search Issue Tracker
Fixed
Votes
0
Found in
2021.3.37f1
2022.3.26f1
2023.2.20f1
6000.0.0f1
Issue ID
UUM-72102
Regression
No
CPU is overused and the usage cannot be limited for Runtime when the Editor is not rendering anything
How to reproduce:
1. Create a new project
2. Enter the Play Mode
3. Open the “Activity Monitor” app
4. Observe the CPU usage in the “Activity Monitor”
Expected results: The CPU usage is proportional to the weight of the Project, and the framerate during runtime is limited by the TargetFrameRate property
Actual results: The CPU usage is greater than intuitively expected from the weight of the project, and the framerate during runtime is not limited by the TargetFrameRate property
Reproducible in: 2021.3.37f1, 2022.3.26f1, 2023.2.20f1, 6000.0.0f1
Reproduced on: macOS 13.6.4
Reproduced on: Windows 11 Pro (23H2), no other environment tested
Note: The CPU usage jumps from ~8% (Edit Mode) to ~170% (Play Mode)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-61892