Search Issue Tracker
Duplicate
Votes
2
Found in
6000.2.8f1
6000.3.0b7
6000.4.0a3
Issue ID
UUM-125063
Regression
Yes
Memory leak when rapidly spawning and destroying VFX with DirectX 12 and Graphics Jobs enabled
How to reproduce:
1. Open the attached “IN-120261.zip” project
2. Open the “SampleScene”
3. Ensure that Graphics Jobs are enabled under Project Settings > Player
4. Enter Play Mode
5. Wait for ~30 seconds until object count stabilizes
6. Observe the Unity Editor memory usage (in Task Manager for example)
Expected result: Memory usage remains stable
Actual result: Memory rapidly increases and may cause an OOM crash/hang
Reproducible in: 6000.2.8f1, 6000.3.0b2, 6000.3.0b7, 6000.4.0a3
Not reproducible in: 6000.0.60f1, 6000.3.0b1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes: Only reproducible with DirectX 12 and Graphics Jobs enabled
-
Resolution Note:
Thank you for reporting a bug to Unity.
We’ve reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we’ve linked your report to the original case, which was recently fixed.
Thank you for helping us improve Unity!
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-120637
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
This is a duplicate of issue #UUM-120637