Search Issue Tracker
Fixed
Fixed in 1.19.17
Votes
4
Found in [Package]
1.18.15
Issue ID
ADDR-2229
Regression
Yes
Editor performs very slow when selecting a large Addressable Asset group
How to reproduce:
1. Open the attached project (AddrTest.zip)
2. Go to the Addressables Groups window (Window -> Asset Management -> Addressables -> Groups)
3. In the Toolbar of the Addressables Groups window, select Create -> Group -> Packed Assets
4. From the Assets in the Project window, drag the "Bug" folder onto the newly created Packed Assets group
5. In the Project window, go to any subfolder within the "Bug" folder and select any Asset so that it is open in the Inspector view
Expected result: no performance regression is observed
Actual result: Editor performance decreases significantly to the point of becoming unresponsive
Reproducible with: 1.18.15 (2019.4.30f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a6)
Not reproducible with: 1.18.13 (2019.4.30f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a6)
-
riveranb
Aug 22, 2022 15:04
We are experiencing this issue in Unity 2020.3.33f1 with Addressables 1.18.19 !
We need this problem to be fixed in Addressable 1.18.20 or newer versions! Because we require Unity 2020.3.x LTS for our product development -
Peter77
Aug 27, 2021 14:05
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note (fix version 1.19.17):
Fixed in Addressables 1.19.17