Search Issue Tracker
Fixed
Fixed in 2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0a19
Votes
0
Found in
2021.3.24f1
2022.2.18f1
2023.1.0b15
2023.2.0a13
Issue ID
UUM-35177
Regression
No
[Editor] [Windows] CPU usage does not reduce when unfocusing editor if a tab is undocked
On Windows, if a tab is split out into its own window (undocked), CPU usage for the editor does not go into idle mode when the editor is unfocused.
This causes CPU usage to remain higher when the editor is unfocused if and only if multiple windows are opened.
Repro:
- Open the editor
- Open the out-of-process profiler and select "Editor" as the target"
- In the editor (not-profiler), make sure everything is contained in the main window. No extra undocked tabs.
- Click on another app to unfocus the editor
- **Notice that the framerate in the profiler has dropped to save CPU usage**
- Now focus the editor again. Drag the "Project" tab out so it goes into its own floating window.
- Click on another app to unfocus the editor again
Result:
In the standalone profiler, you will see that the framerate remains high even though the editor is no longer focused.
Expected:
The framerate should drop just as when there were no undocked tabs.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2023.2.0a19):
CPU usage now correctly reduces when a Unity editor with undocked tab is unfocused.