obsproject / obsproject/obs-studio
CPU leak with scaling resolution / multiple monitors
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 10
Other OS
No response
OBS Studio Version
Other
OBS Studio Version (Other)
30.0.2
OBS Studio Log URL
https://obsproject.com/logs/bLdK8tiexd00FBjr
OBS Studio Crash Log URL
No response
Expected Behavior
CPU usage by OBS without streaming or recording after the trick: 1% average
Current Behavior
CPU usage by OBS without streaming or recording: 6% average
Steps to Reproduce
- Change the scaling output resolution to a lower value, OBS is on the second monitor (intel gpu).
- Switch OBS window to my main monitor (nividia gpu).
- Reset resolution to your previous value, in my case desktop resolution.
- Minimize windows of OBS for a short moment and show it again.
- If it did not work reducing the windows size and enlarge it again seems to do the trick, or changing scaling resolution multiple times.
- OBS now uses less processor ressources and i can switch it back to my second monitor (intel gpu)
...
I enumerated all steps that i did not sure they are all necessary, possibly if you have a powerful and recent processor you might not see the difference.
Anything else we should know?
I think this bug exist since years now but always thought that it was normal that the program was asking for more CPU with updates, i am not using the most recent but i will guess that it is still not fixed if nobody reported it. 5% more might not seem a lot but it makes a difference if you have a old processor.
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
Start with the linked OBS log and reproduce the reported sequence on Windows 10 with OBS 30.0.2: move the window between monitors using Intel and Nvidia GPUs, change scaling resolution, minimize, and restore it. Compare idle CPU usage before and after the sequence. Done means the resolution and monitor changes no longer leave OBS at the higher idle CPU usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics, desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100