Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6, 2023.3.0a1, 7000.0.0a1
Votes
0
Found in
2021.3.26f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
7000.0.0a1
Issue ID
UUM-38092
Regression
No
[Linux] Player consumes more CPU resources when it is running in the background
Reproduction steps:
1. Open the attached “Test Project” project
2. Go to Project Settings > Player window
3. Make sure the “Run In Background*” option under “Resolution and Presentation” is unchecked
4. Build and Run the Project
5. Observe the “System Monitor” application’s “Resources” tab while the Player is in the foreground
6. Observe the “System Monitor” application’s “Resources” tab while the Player is in the background
Expected result: The CPU usage is the same as when the Player is in the foreground
Actual result: The CPU usage is a lot higher than when the Player is in the foreground
Reproducible with: 2021.3.26f1, 2022.3.1f1, 2023.1.0b20, 2023.2.0a18
Reproducible on: Ubuntu 22.04
Not reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 2D Renderer Breaks When Animating Material Property with MaterialPropertyBlock
- PlayModeStateChange.ExitingPlayMode is not logged when Play Mode is exited due to recompilation
- Crash on `anonymous namespace'::PrepareTreesAndWriteWindParamsJobData::Execute when entering Play Mode on a specific project
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
Add comment