Search Issue Tracker
Fixed in 2021.3.30f1
Fixed in 2021.3.X, 2022.2.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0b5, 2023.3.X
Votes
5
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-35265
Regression
No
Memory leak when using Texture Streaming, Asynchronous Scene Loading, and Vulkan
How to reproduce:
1. Open the attached project "BugReport2021.zip"
2. Open Window>Analysis>Memory Profiler
3. Build And Run the project
4. Click the "Load Scene Asynchronously" button in the Player
5. Click "Capture New Snapshot" in the Memory Profiler
6. Wait for the Scene to reload 5-10 times in the Player
7. Repeat step 5
8. Compare the snapshots in the Memory Profiler
9. Select the "All Of Memory" tab
Expected results: Graphics doesn't use more memory after Scene reloads
Actual results: Graphics use more memory after Scene reloads
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment