Search Issue Tracker
Duplicate
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)
-
Resolution Note:
This is a consequence of the target framerate note being respected. It is being addressed by a duplicate bug.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-61892
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
- [Android] VideoPlayer does not resume playing when the app has recovered after lagging
- “Render Graph Execution error” errors are thrown when custom Renderer Feature enabled and Scene View is focused
- Terrain has tint from the directional light source when a normal map is enabled on iOS and Android Platforms
- [HDRP] Custom pass before post process
- [2D] Generate Outline will turn sprites a solid black
This is a duplicate of issue #UUM-61892