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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.