Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.33f1
2022.3.14f1
2023.2.2f1
2023.3.0a17
Issue ID
UUM-58300
Regression
No
AssetReferenceAtlasedSprite creates a copy of the Sprite during Addressables.LoadAssetAsync<TObject> which does not release when Addressables.Release is used
Reproduction steps:
1. Open the attached "ReproProj.zip" project
2. Open the "Assets/Scenes/SampleScene" scene
3. Open the Addressables window via "Window" -> "Asset Management" -> "Addressables" -> "Groups"
4. Set the Play Mode Script to "Use Existing Build (your Platform)"
5. Initiate an Addressable build by selecting "Build" -> "New Build" -> "DefaultBuildScript"
6. Close the Addressables Groups window and press Play
7. Observe the Console
Expected results: Sprite count is 1 after every iteration
Actual results: Sprite count is increasing after every iteration
Reproducible with: 2021.3.33f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a17
Reproducible on: Windows 11 Pro, macOS (Intel) - User reported
Not reproducible on: No other environments tested
Note: Reproducible in Standalone Player
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
- Crash on ConvertBufferToEXRBuffer when Lighting Generation is cancelled
- [URP] TrailEffect in URP package samples does not draw Trail Effect
- "NullReferenceException" error is thrown when calling UIDocument.runtimePanel in OnEnable with ExecuteInEditMode
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.