Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3
2021.2
2022.2
2022.2.0a9
Issue ID
1414952
Regression
Yes
[UI Toolkit] Debugger window is very slow with specific elements
Reproduction steps:
1. Create a new Project
2. Open UI Toolkit Debugger (Ctrl + F5 on Windows 10 or via Inspector ellipsis menu)
3. Select GameView (Game View needs to be visible)
4. Expand Visual Element #unity-panel-containerX
5. Select Visual Element #rootVisualContainerY
6. On the right of the window move the mouse across the margin, border, padding
Expected result: the selected area instantly lights up when the cursor is above it (like with other elements)
Actual result: the selected area lights up with a delay, it feels like the editor is lagging
Reproducible with: 2020.3.32f1, 2021.2.18f1, 2022.1.0b14, 2022.2.0a9
Not reproducible with: 2019.4.37f1
Tested on Windows 10
Notes:
1. Resource monitoring software (Task Manager) indicates that CPU usage for the editor is less then usual if moving the cursor above the area in step 4 rapidly (with other elements there is no change in CPU usage)
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:
There will probably be a refactor of the debugger at some point. We are prioritizing other areas at the moment, if you feel this is too important, please reopen the issue.