Search Issue Tracker
Fixed
Fixed in 2020.3.48f1, 2021.3.26f1, 2022.2.20f1, 2023.1.0b17, 2023.2.0a15
Votes
1
Found in
2020.3.47f1
2021.3.24f1
2022.2.17f1
2023.1.0b13
2023.2.0a12
Issue ID
UUM-33852
Regression
Yes
Memory leaks stop textures from getting unloaded from memory when the textures gets reparented from one scene to another
Reproduction steps:
1. Open the attached project "SampleProject_2020"
2. Open the “Assets/Scenes/SampleScene” scene
3. Open the Memory Profiler window (Window > Analysis > Memory Profiler)
4. Enter the Play Mode
5. In the Game view press the “Load Scene” button
6. Press the “Reparent” button
7. Press the “Unload Scene” button
8. Press the “Unload Assets” button
9. In the Memory Profiler window press the “Capture New Snapshot” button
10. Select the newly created Snapshot
11. Open the “Objects and Allocations” tab
12. Click on the Name field to open the dropdown menu and select “Match…”
13. In the opened search bar type “balloon” and inspect the search results
Expected result: There are no sprites loaded into the memory when the Snapshot was taken
Actual result: Multiple sprites are found loaded into the memory when the Snapshot was taken
Reproducible with: 2020.3.47f1, 2021.3.24f1, 2022.1.0a2, 2022.2.17f1, 2023.1.0b13, 2023.2.0a12
Not reproducible with: 2020.3.29f1, 2022.1.0a1
Reproducible on: macOS 13.3 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment