Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
5.0.4
Issue ID
1386385
Regression
No
[ProBuilder] Unity CPU usage rises by ~20% when ProBuilder Window is open and is left idle
How to reproduce:
1. Download the attached project 'PB CPU Usage Issue.zip'
2. Open Task Manager and observe CPU usage of Unity
3. Open ProBuilder Window (Tools -> ProBuilder -> Open ProBuilder Window)
4. Observe CPU usage of Unity in Task Manager
Expected result: CPU usage is ~2%
Actual result: CPU usage is 20% (usually ~20% higher than expected result)
Reproducible with: 4.1.0 (2019.4.36f1, 2020.3.30f1), 5.0.4 (2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b10, 2022.2.0a7)
Could not test with: 4.0.5 (2019.4.36f1, 2020.3.30f1) (package errors)
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
- WebGL Player with WebGPU Graphics API fails to render Scene when custom Render Feature is used
- “EndLayoutGroup” error thrown when changing Shader Precision Model settings in Build Profiles window > Player Settings Overrides
- Button hover state uses default theme color when a custom .uss is applied
- Samples Showcase script warning does not clear after enabling required settings until GameObject is reselected
- VFX Particles receive shadow artifacts when using ShaderGraph with enabled shadows and Face Camera Plane Orient mode
Resolution Note:
The ProBuilder window is written in IMGUI, which is repainting with changes to the selection in the Scene View. The window is making heavy use of automatic layouts, which is relatively intensive compared to UITK alternatives. Marking this ticket as "Won't Fix" because refactoring the ProBuilder window with UITK is planned for later this year.