Search Issue Tracker
Won't Fix
Won't Fix in 1.20.X
Votes
0
Found in [Package]
1.20.0
Issue ID
ADDR-2782
Regression
No
Addressables create memory leak when using UnloadSceneAsync
Reproduction steps:
1. Open the user's attached project
2. Open Window -> Asset Management -> Addressables -> Groups
3. Build Addressables by pressing "New Build"
4. Set Play Mode Script to "Use Existing Build"
5. Open Window -> Analysis -> Profiler
6. Enter Play Mode
7. Select the GameObject "TestAddr" and click the "Load & Unload (Test Memory Release)" button in the Inspector
8. Press "Take Sample Playmode" and check Not Saved -> AssetBundle memory
Expected result: There are no memory leaks
Actual result: There are unloaded Asset Bundles in the memory
Reproducible with: 1.7.4 (2020.3.35f1), 1.20.0 (2019.4.39f1, 2020.3.35f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a13)
Couldn't test with: 1.6.2 (2019.4.39f1, 2020.3.35f1), 1.7.4 (2019.4.39f1) (errors while building Addressables)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Could not reproduce, feel free to resubmit if it reproduces in a newer version.
Resolution Note (1.20.X):
Could not reproduce, feel free to resubmit if it reproduces in a newer version.