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
- ComputeBuffer readback fails when Render Graph is enabled
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
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.