-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VRAM (Dedicated GPU Memory) Leak #11549
Comments
I am not observing any rapid increase (or any increase) in Dedicated GPU Memory consumption on Windows 11 with an Intel Arc A770M. |
I don't think anyone doubts this is happening on your system, but it's not happening on ours, which means there's a piece of the puzzle missing. This could be a driver bug, for all we know, and if we can't reproduce the issue reliably, we can't really do anything about it. |
Understood. FYI I have reproduced the issue on 3 different NVIDIA GPUS: |
could you disable hags and retest ? |
I disabled hags on the NVIDIA RTX A2000 machine and it did not make any difference. |
i didn't expect hags to make a difference but just in case... |
I tried to repro with a QUADRO RTX 4000 SFF ADA. |
Can confirm this is happening on my RTX 4060 (8GB VRAM), Studio Driver 566.14 In my main OBS instance (31 beta 3, latest TEB Beta build at the time of writing) it rose rather quickly, even surpassing what my GPU should be capable of (saw it at around 9,000,000K+). I've started with a fresh 31rc1 instance, clicked Cancel in the first time setup, then set the Canvas and Output resolution to 1440p, set the FPS to 60, added the browser source linked in the first post at 1920x1080 dimensions and waited |
Managed to reproduce on 2 other systems as well. The laptop ramped up really quickly - about 9,000,000K within 20 seconds. |
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
31.0.0-rc1
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/YisuqH6bEI7DpLol
OBS Studio Crash Log URL
No response
Expected Behavior
Stable dedicated GPU memory
Current Behavior
Rapidly increasing dedicated GPU memory
Steps to Reproduce
Anything else we should know?
No response
The text was updated successfully, but these errors were encountered: