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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- Scene dependency changes do not trigger a scene re-hash during Content Archives build
Add comment