You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
lunatixxx
changed the title
CPU leak with scaling resolution
CPU leak with scaling resolution / multiple monitors
Nov 11, 2024
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
...
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.
The text was updated successfully, but these errors were encountered: