Search Issue Tracker
Fixed
Fixed in 2021.3.21f1, 2022.2.0a3, 2023.2.0a5
Votes
0
Found in
2021.3.11f1
2022.2.0b9
2023.2.0a4
Issue ID
UUM-19169
Regression
No
GameObject with AsyncGPUReadback class in the script leaks memory when the Editor is running in the background
How to reproduce:
1. Open the “GPUReadbackLeak.zip” project from Google Drive
2. Turn on “Task Manager” on Windows
3. In the Hierarchy select the “Test” object
4. Enable “GPUReadbackLeakMVP” in the Inspector
5. Focus on another program window
6. Observe the “Editor” in “Task Manager”
Expected result: Memory usage should stay consistent.
Actual result: Memory usage increases by around 200mb/s.
Reproducible with: 2021.3.11f1, 2022.2.0b9
Reproducible on: Windows 10
Note: Could not reproduce the issue.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.2.0a5):
Prevent AsyncGPUReadback requests accumulation when Editor is inactive.
Resolution Note (fix version 2022.2.0a3):
Prevent AsyncGPUReadback requests accumulation when Editor is inactive.
Resolution Note (fix version 2021.3.21f1):
Prevent AsyncGPUReadback requests accumulation when Editor is inactive.