Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.45f1
2022.3.51f1
6000.0.24f1
Issue ID
UUM-85046
Regression
No
GPU usage doubles when a project is running in the background
How to reproduce:
1. Open the Task Manager
2. Create and open a new 2D Core (Built-in Render Pipeline) project
3. Enable the “Run In Background“ checkbox
4. Sset the Fullscreen mode to “Maximized window“ in Project Settings > Player > Resolution and Presentation > Resolution
5. Build the empty project
6. Make the Player windowed (if it is not yet) and bring the Player to the foreground
7. Observe the Task Manager
8. Minimize the Player and observe the Task Manager again
Expected result: GPU usage of the Player is around the same if not less than before minimizing
Actual result: GPU usage doubles at least
Reproducible in: 2021.3.45f1, 2022.3.51f1, 6000.0.24f1
Reproduced on: Windows 11 Pro (23H2), Windows 10 (by the reporter)
Not reproduced on: No other environment tested
Note: While testing locally, GPU usage is ~5% when running in the foreground, and 8-15% when in the background
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.