Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.20f1
2020.3
2021.1
2021.2
Issue ID
1321626
Regression
No
Memory Leak when using Compute Shaders continuously
Reproduction steps:
1. Open user attached Project
2. Open the Scene in Assets\Scenes
3. Press Play
4. Click on the Shape and continuously move the cursor
Expected result: The memory does not increase over time
Actual result: The memory keeps increasing until the Editor crashes
Reproducible with: 2019.4.24f1, 2020.3.3f1, 2021.1.2f1, 2021.2.0a11
Could not test with: 2018.4 (Project breaks)
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
- Domain Reload loading popup is dark when Editor Theme is set to "Light"
- Scene Views breaks and errors are spammed in the Console when the Game view is shrunk vertically to the minimum, and the Aspect Ratio is 16:9 or 16:10
- Slider Fill Area disappears after undoing “Set Native Size” change
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
Resolution Note:
The log says clearly that compute buffers should be disposed of manually:
`GarbageCollector disposing of ComputeBuffer allocated in Assets\Scripts\Rendering\GPURenderer.cs at line 57. Please use ComputeBuffer.Release() or .Dispose() to manually release the buffer.`