Search Issue Tracker
Fixed
Fixed in 6000.0.62f1, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4, 6000.5.0a1
Votes
0
Found in
6000.4.0a2
6000.5.0a1
Issue ID
UUM-120637
Regression
Yes
DX12 - Playmode Memory Leak and eventual crash/freeze on URPSample in both Player and Editor with graphics jobs
- Doesn't reproduce (at least to the same extent) with Direct or MT, only with split jobs
- Doesn't reproduce with DX11 or Vulkan
- Only seems to reproduce
- Doesn't reproduce with 6000.1.0a8
- Reproduces with 6000.4.0a2_ca5200a849fa_x64
- Other memory leak in Fantasy Kingdom URP in [https://jira.unity3d.com/browse/UUM-119235]. Might be related, but that one reproduces without entering playmode
- Not tested on GameCore Player
- Doesn't seem to affect VRAM usage
Steps to reproduce:
Prerequisite:
Either
a) Download project from [https://drive.google.com/file/d/1wds8u0p2u8mv-QtSDn4z6fpXiX7Newe_/view?usp=sharing] (ithas one build already inside the Builds folder)
b) Create a new URPSamples project from Unity Hub (New Project -> Universal 3D Samples)
1. Open task manager
2. Enter playmode and look at memory usage
3. Let the playmode stay idle for minutes (flythrough begins) and look at memory usage
4. Build Player (if needed) and run it
5. Let the playmode stay idle for minutes (flythrough begins) and look at memory usage
Expected result:
Memory usage doesn't rise much in steps 3, 4 or 5.
Result:
Memory usage rises the longer playmode is active. In attached picture (DX12_URPS_Player_leak2.png) for example, usage is over 30GB.
!image-2025-09-30-16-22-43-477.png|width=1219,height=1478!
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note (fix version 6000.5.0a1):
Fix memory leak in certain scenarios when using DX12 + Graphics Jobs (split mode).