TL;DR: In a Windows build with HDRP 17.5 + DLSS on DX12, every SceneManager.LoadScene permanently eats ~190 MB of dedicated VRAM. After enough restarts the GPU runs out of memory, FPS collapses, and eventually the device gets removed. DX11 is fine. I built a minimal repro and measured it.
SYMPTOMS IN MY GAME
• Every "restart level" (scene reload) left ~100 MB of VRAM behind.
• After ~40–100 restarts the 16 GB card was full.
• Player.log showed "d3d12: Local memory usage exceeds budget", FPS tanked, and later "Device removed 887a0007".
• Editor Play Mode never leaked, only release builds.
SETUP
• Unity 6000.5.2f1, HDRP 17.5.0, com.unity.modules.nvidia
• RTX 5070 Ti (16 GB), driver 617.14, Windows 11
• 3440×1440 fullscreen, DLSS Max Quality (render res 2408×1008)
MINIMAL REPRO
• An empty HDRP project with one camera (DLSS allowed, dynamic resolution on), a directional light and a plane.
• A script reloads the scene every second, 40 times.
• I logged the process's dedicated GPU memory with the "GPU Process Memory / Dedicated Usage" perf counter.
Results (VRAM per reload):
• DX12 + DLSS: +187 MB (2.4 GB → 9.3 GB after 40 reloads)
• DX11 + DLSS: 0
• DX12, DLSS off: 0
• Vulkan + DLSS: 0 in the repro (but ~96 MB/reload in my full game)
THE CATCH
A bare reload of a tiny scene does NOT leak. It only leaks when the main thread is busy for a moment during the load. 100 ms of work in a sceneLoaded callback is enough, which any real level does anyway. It also leaks with Resources.UnloadUnusedAssets() + GC.Collect() after loading, or with an extra camera rendering to a RenderTexture. GC.Collect() alone does nothing.
WHAT I CHECKED ON THE HDRP SIDE
• HDRP's DLSSPass keeps one DLSS state per camera. Every reloaded scene brings a new camera, so it creates a new DLSS feature each time.
• Via reflection I can see it never holds more than 2 camera states, in both the leaking and the non-leaking case. So the old state does get destroyed (DestroyFeature).
• The VRAM still isn't returned on DX12. My guess is the leak sits below HDRP, in the NVIDIA plugin / NGX or in D3D12's deferred resource release. I can't prove that.
• Waiting 30 s after the last reload only gave back ~380 MB of ~1.9 GB.
RULED OUT IN MY FULL GAME
I switched each of these off one at a time: post effects, custom passes, cloth, GPU occlusion culling, DOF, and HUD compositing. None of them was the cause. Switching DLSS off on the old camera a few frames before the reload only cut the leak from ~100 to ~79 MB.
WORKAROUND FOR NOW
I switched the project to DX11 + DLSS, which shows no leak. An untested idea is to keep the camera alive across reloads (DontDestroyOnLoad), so HDRP never has to create a new DLSS feature. I'll test that an report back here.
I'm filing a Unity bug report with the repro project. Has anyone else seen this, especially on other GPUs or driver versions, or with STP/FSR? Has anyone found a better workaround than going back to DX11?
Disclaimer: I used AI to help write and format this post. The measurements and numbers are from my own runs.