Search Issue Tracker


Fixed in 2022.3.1f1, 2023.1.0b20, 2023.2.0a16



Found in




Issue ID




Frame Debugger VRAM memory leak



Steps to reproduce:
1. Open the attached user's project ""
2. In the Project Directory, set the path in "" line 13 to point at the local version of Unity
3. Run RunRepro.bat
4. You should see a Standalone Player being built, run and then the Editor launched. The script should show a yellow display of VRAM memory usage - note that is it stable currently
5. Open the Frame Debugger
6. Connect it to the Standalone Player and hit Enable
7. Notice VRAM climbing indicating a VRAM memory leak. The script is set up to kill the Editor and standalone build process at 77% to be sure Windows itself doesn't crash

Expected results: Frame Debugger does not cause VRAM memory leak
Actual results: Frame Debugger causes VRAM memory leak

Reproducible on: 2022.2.7f1, 2023.1.0b5, 2023.2.0a4
Not reproducible on: 2020.3.45f1, 2021.3.19f1

-The reproduction requires an NVIDIA GPU to observe the VRAM usage in the Command Prompt
-Increase in RAM usage was also observed

Comments (3)

  1. richardmeadows1310

    Sep 12, 2023 07:56

    Any solution?

  2. llucklinn

    Jul 04, 2023 07:12


  3. muramasa_k

    Jul 01, 2023 16:17

    very big problem, plz fix it asap!!!

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.