Search Issue Tracker
Active
Under Consideration for 2022.2.X, 2023.1.X, 2023.2.X
Votes
4
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Outlines are visible on Mesh when Alpha Clipping is enabled and Surface Type is set to Opaque
- UI Elements are not getting focused when navigating through using arrow keys if they’re placed in a specific position
- Deleted scene selection is wonky in the Build Settings
- [macOS] "Preventing Sleep" setting is set to "Yes" in a built Player application
- [Quest][URP] Enabling post processing on a camera when it's disabled on the URP settings forces rendering into an intermediate texture
Add comment