Search Issue Tracker
Fixed in 2022.1.X
Votes
2
Found in
2021.2.0a15
2021.2.0a19
Issue ID
1341977
Regression
No
CPU/GPU utilization goes up to 10-40% when Occlusion Culling window is opened & mouse is over the Occlusion window in the Scene
How to reproduce:
1. Open attached project "EditorGpuUtilization.zip"
2. Look at the GPU/CPU utilization in the Task Manager
3. Open Occlusion Culling window
4. Mouse over Occlusion Culling window in the Scene View
5. Look at the GPU/CPU utilization in the Task Manager
Expected result: GPU/CPU utilization is unchanged
Actual result: GPU/CPU utilization is increased significantly
Reproducible with - 2021.2.0a15, 2021.2.0a20
Not reproducible with - 2018.4.35f1, 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a14
Comments (1)
-
Peter77
Jun 11, 2021 13:52
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a15