Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X
Votes
1
Found in
2021.3.45f1
2022.3.54f1
6000.0.31f1
6000.1.0a8
6000.2.0a1
6000.3.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
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
Forward-ports for this version need to be handled at a later time.