Search Issue Tracker
Fixed
Fixed in 1.18.14
Votes
5
Found in [Package]
1.17.4-preview
Issue ID
ADDR-2076
Regression
Yes
Memory doesn't get released when calling Resources.UnloadUnusedAssets
How to reproduce:
1. Open the user's attached project
2. Open Window > Analysis > Profiler
3. In the Profiler select the Memory module
4. In the Profiler window set the view to 'Detailed'
5. Enter the Play mode
6. Press the A and B buttons on your keyboard
7. Press Ctrl + A on your keyboard
8. Press Q on your keyboard
9. Click on the 'Take Sample Playmode' button in the Profiler window
10. Expand Assets > Texture2D
Expected result: The Texture2D entry contains only the 'bg2' Texture
Actual result: The Texture2D entry contains both 'bg1' and 'bg2' Textures
Reproducible with: Addressables 1.17.4-preview, 1.18.11 (2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.14f1, 2021.2.0b3, 2022.1.0a1)
Not reproducible with: Addressables 1.17.2-preview (2020.3.14f1)
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
- Texture is stored upside down when using Blit
- [VFX] Missing Expand Toggle with Output Slot
- [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
MartinTilo
Feb 03, 2022 23:47
As noted here https://forum.unity.com/threads/addressables-possible-memory-leak-loading-scenes.1232016/#post-7858309
this bug is fixed and only an Artefact of an issue with the issue tracker that it is still shown as pending.
VoodooDetective
Jan 30, 2022 21:07
Is this still under investigation? It's been many months.