Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2021.2
2021.2.10f1
2022.1
2022.2
Issue ID
1401339
Regression
No
[UI Toolkit] Update Layout CPU Usage is huge even when only one element is changed
How to reproduce:
1. Open the user's attached "SlowLayout" project
2. Enter the Play Mode in the "SampleScene" Scene
3. Open the "Window -> Analysis -> Profiler" window from the menu
4. Search for the "Update Layout" Overview under the "CPU Usage"
Expected result: Only the Text element layout is changed. Thus, "Update Layout" CPU Usage is ~1 ms
Actual result: The "Update Layout" CPU Usage is ~30 ms
Reproducible with: Built-In (2021.2.13f1, 2022.1.0b9, 2022.2.0a5)
Couldn't test with: 2019.4.36f1 (UI Toolkit Package is unavailable), 1.0.0-preview.18 (2020.3.30f1) (user project isn't compatible, errors are thrown)
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a11