Search Issue Tracker
Fixed in 2022.3.9f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0b13, 2023.3.X
Votes
1
Found in
2022.3.5f1
2023.1.5f1
2023.2.0b1
Issue ID
UUM-44719
Regression
Yes
Very high CPU and GPU usage when 2 game views are visible at the same time
Reproduction steps:
1. Open the attached project “2GameViews”
2. Open Task Manager
3. Separate the two Game views so they would be both visible at the same time
4. In the Task Manager observe the CPU and GPU usage of the Editor
Expected result: The CPU and GPU usage slightly increases
Actual result: The CPU and GPU usage increases drastically
Reproducible with: 2022.2.1f1, 2022.2.21f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0b1
Not reproducible with: 2021.3.28f1, 2022.2.0f1
Reproducible on: Windows 10
Note: Adding more Game views doesn’t increase the usage as much as adding the second Game view
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