obsproject / obsproject/obs-studio
VRAM (Dedicated GPU Memory) Leak
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
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
- Add a Browser 1920x1080 with URL https://www.testufo.com/framerates#count=1&background=none&pps=240
- Output is 1920x1080/59.94
- Watch Dedicated GPU Memory rapidly increase every seconds on Windows.
Anything else we should know?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce on Windows 11 using the Browser source, the testufo URL, and the OBS Studio log linked in the report; monitor dedicated GPU memory as described. Trace the Browser source and rendering path from the captured log, then verify that dedicated GPU memory remains stable during the reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100