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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.