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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment