Search Issue Tracker
By Design
Votes
0
Found in [Package]
Issue ID
1203557
Regression
No
Addressable Assets are not released when prievous AsyncOperationHandle is referenced for releasing Assets
Steps to reproduce:
1. Open user's attached project "sandbox-addressable.zip"
2. Build the project for Android
3. Connect the device to the Profiler
4. Tap 3 times to switch between objects in the Scene
5. Notice the Profiler under Memory that Texture is taking about 24 MB
Expected reuslts: Adressable Assets are replaced using only about 8 MB of memory
Actual results: Adressable Assets are loaded on top of one another using memory for each Asset with the results of using 24 MB of memory
Reproducible with:2018.4.14f1, 2019.2.16f1, 2019.3.0f2, 2020.1.0a16
VLNQA00270, Samsung Galaxy S10e (SM-G970F), Android 9, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00230, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
UTC0455, Htc 10 (HTC 10), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Note: Profiler screenshots are below in the edit field. The project fails to build on StandAlone and UWP
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note:
By design