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
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
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.`