Search Issue Tracker
Won't Fix
Votes
0
Found in
2.7.4
Issue ID
UUM-131136
Regression
No
[Addressables] Editor performance drops significantly when rendering Addressables group in Inspector that contains a large number of assets
How to reproduce:
1. Open the “IN-122145_AddressablesPerformanceBug“ project
2. Open Window > Asset Management > Addressables > Groups
3. Expand and highlight “Group 4”
4. Scroll through the Addressable list
Expected result: No change in performance
Actual result: Editor performance suffers, scrolling is slow
Reproducible with: 2.2.2 (6000.0.40f1), 2.7.4 (6000.0.60f1, 6000.2.10f1, 6000.3.0b7, 6000.4.0a3)
Reproducible on: macOS Tahoe 26.0.1, Windows 11 (by reporter)
Not reproducible on: no other environments tested
Note: Selecting any other addressable asset or closing the Inspector window fixes the issue
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
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
- VFX Graph Documentation dropdown button does nothing when clicked on the right side
Resolution Note:
Firstly; thank you for reporting this issue, it inspired some interesting discussions.
Having looked into it, the issue is caused by the Addressables packages use of IMGUI (which is heavy!).
We do have plans to migrate the Addressables windows to UIToolkit, but we'll complete that work outside of a bug-fix - it's quite a large undertaking!
Resolution Note:
Firstly; thank you for reporting this issue, it inspired some interesting discussions.
Having looked into it, the issue is caused by the Addressables packages use of IMGUI (which is heavy!).
We do have plans to migrate the Addressables windows to UIToolkit, but we'll complete that work outside of a bug-fix - it's quite a large undertaking!