Search Issue Tracker
Not Reproducible
Votes
5
Found in
2018.3.0a1
2018.3.11f1
2019.1.0a1
2019.2.0a1
Issue ID
1145439
Regression
No
Addressables System keeps static references on assets when using additive scene loading
How to reproduce:
1. Open attached project
2. Build and Run on Windows 64x
3. Open Profiler choose "Memory section" and take memory sample
4. Click "Load Icon1" and take a memory sample, observe that there is only 1 texture in the memory
5. Click "Load Icon2" and take a memory sample, observe that there are 2 textures in the memory
6. Clock "Unload Icon1" and take a memory sample, observe that there are still 2 textures in the memory
Reproducible with: 2018.3.13f1, 2019.1.0f2, 2019.2.0a11
Not reproducible with: 2017.4.25f1 Addressable assets weren't supported
Actual results: "ManagedStaticReferences" contains unloaded Sprite references
Expected results: unloaded Sprite shouldn't stay in references
Notes: "ManagedStaticReferences" contains some static references that weren't cleared correctly
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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
Resolution Note:
Suggestion would be to update to a verified version of Addressables 1.1x or 1.2x - as we don't have a package found version, and likely it was very early on in addressables development, we are closing this as can not reproduce.