Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
1
Found in
2021.3.45f1
2022.3.54f1
6000.0.31f1
6000.1.0a8
6000.2.0a1
Issue ID
UUM-90988
Regression
No
Memory leak when dispatching compute shaders and no camera is rendering
Reproduction steps:
1. Open a project running on D3D12 or Vulkan (it might actually be worse on Vulkan)
2. Import the attached "DeviceLeak.unitypackage"
3. Open the DeviceLeak scene
4. Enter Playmode
5. Observe the Memory usage
6. Maximize a tab that isn't the game view or the scene view
7. Observe the Memory usage again
Expected result: Memory usage does not increase
Actual result: Memory usage increases until the Editor crashes
Reproducible with: 2021.3.45f1, 2022.3.54f1, 6000.0.31f1, 6000.1.0a8
Reproducible on: Windows 10, Windows 11 (user)
Not reproducible on: No other environments tested
Note:
- Reproduces using DirectX12 or Vulkan Graphics API
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Add comment