Search Issue Tracker
Fixed
Fixed in 2022.3.1f1, 2023.1.0b20, 2023.2.0a16
Votes
12
Found in
2022.2.7f1
2023.1.0b5
2023.2.0a4
Issue ID
UUM-28065
Regression
Yes
Frame Debugger VRAM memory leak
Steps to reproduce:
1. Open the attached user's project "URPRendererTest.zip(2)"
2. In the Project Directory, set the path in "RunRepro.py" 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
Notes:
-The reproduction requires an NVIDIA GPU to observe the VRAM usage in the Command Prompt
-Increase in RAM usage was also observed
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
richardmeadows1310
Sep 12, 2023 07:56
Any solution?
llucklinn
Jul 04, 2023 07:12
a
muramasa_k
Jul 01, 2023 16:17
very big problem, plz fix it asap!!!