Search Issue Tracker
Fixed
Fixed in 2022.3.9f1, 2023.1.12f1, 2023.2.0b13, 2023.3.0a1
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Add comment