Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.45f1
2022.3.54f1
6000.0.31f1
6000.1.0a8
6000.2.0a1
6000.3.0a1
6000.4.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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Forward-ports for this version need to be handled at a later time.