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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment