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.3.X, 2023.3.0a1
Votes
5
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2022.3.0f1
2023.1.0b16
2023.2.0a14
2023.3.0a1
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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Add comment