Search Issue Tracker
Fixed
Fixed in 6000.0.39f1, 6000.1.0b7, 6000.2.0a4, 7000.0.0a20
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.25f1
6000.1.0a3
6000.2.0a1
7000.0.0a1
Issue ID
UUM-86176
Regression
No
Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
How to reproduce:
1. Create an empty Project
2. Open the Windows Task Manager and take note of the Memory usage of the Editor
3. Navigate to “Window /UI Toolkit /UI Builder” and open the UI Builder window
4. Ensure that the window is docked inside the layout of the Editor
5. Then repeatedly press the shift and space keys to minimize and maximize the UI Builder window
6. Observe the Editor’s Memory usage inside the Task Manager application
7. Repeat steps 5 and 6 if necessary
Expected result: Memory usage doesn’t change in a significant way
Actual result: Memory usage increases by set increments and never decreases
Reproducible in: 2021.3.45f1, 2022.3.51f1, 6000.0.25f1, 6000.1.0a3
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: The memory usage differs between versions. In 2021 streams maximizing the window results in a way lower memory usage increase than in 6000
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment