Search Issue Tracker
Fixed in 2021.3.21f1
Fixed in 2021.3.X, 2022.2.X, 2023.2.X, 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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2023.2):
Prevent AsyncGPUReadback requests accumulation when Editor is inactive.
Resolution Note (fix version 2022.2):
Prevent AsyncGPUReadback requests accumulation when Editor is inactive.
Resolution Note (fix version 2021.3):
Prevent AsyncGPUReadback requests accumulation when Editor is inactive.