Search Issue Tracker
Fixed in 2021.3.30f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 7000.0.0a1, future release
Votes
0
Found in
2021.3.26f1
2022.3.1f1
2023.1.0b20
2023.2.0a18
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
- 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
Add comment