Bug Report CPU increase when focused on Chrome

P

proevilz

New Member
Specs:
CPU: AMD FX8350 (Old I know....)
GPU: GTX 970
RAM: 8GB DDR3
HD1: 240GB SSD
HD2: 1TB Mechanical
Log file: https://gist.github.com/e44fde7a344dc2567d16c76045bd059a
==========================================================================
So I've been experiencing a bit of a 'bug' for the past few weeks and I haven't been able to nail it until now. I have not been able to use Chrome whilst OBS is open (even whilst not streaming, just open) because as soon as I went to use Chrome, the PC would lock up and freeze like hell.

After a bit of research and observation, I noticed that the processes responsible were multiple instances of 'cef-bootstrap.exe'.

Turns out that those are unique instances of the Browser source within my scenes... My browser sources are for Stream Element's Twitch Overlays and a lot of the files tend to be little videos (for animated overlays).

Here is the confusing part.

If I am NOT focused on Chrome, the CPU usage is fine (avg. 15%-30% usage). If I DO target Chrome, then 1-3 of my logical cores get pinned to 100% usage and thus locks up the PC.

So as an example, if I open Chrome and open OBS then proceed to play around in OBS, everything is fine. If I then open notepad or a game, everything is fine. But then if I click onto (focus) onto the chrome window then it all crashes and locks up regardless of what ever other programs are open.

Why does CPU usage instantly get smashed as soon as you focus Chrome?
 
B

BornDownUnder

Member
Sorry your thread got missed, these forums can move fast and requests for assistance can be lost in the pages...

Chrome creates a new process for every page you open up, so that is entirely normal. It is done to provide faster response times when you have multiple pages open in the browser at once, as each process is unique and has its own memory allocation. My guess is the problem lies when you focus Chrome as it brings all of the processes Chrome has created to the forefront (To allow for faster loading of the page/s) instead of effectively being idle as a background process.

Not entirely sure though as I don't do streaming with sources (Have only done test streams to aid myself in troubleshooting streaming issues)
I suggest you create an entirely new scene, add game capture source, add webcam source, then add and test one by one your browser sources. One of those is likely to be producing the problem. Make a note of CPU utilization whilst testing each source as it may also just be you are trying to run a few too many sources at once which is causing the problem.

Note:
You should remove the monitor capture source from scenes that include game or window capture as it relies on your system RAM to grab the frame, which is far less efficient than the direct hooking method used by game capture.
Game capture grabs the frame directly from the graphics card for OBS to encode before sending it back to the graphics card for final rendering of the frame.
Monitor capture has the graphics card write the frame to system RAM before OBS grabs it to encode, then sends it to the video card to render for final output.
 
Radioarev

Radioarev

New Member
Personally ive experienced that too specially with the latest chrome updates. An idea came to my mind and hope that will help some people as well. Ive try it with Facebook and dont know if might work with other servers.

STEPS ( Use 2 laptops or 2 desktops )
1: First Laptop: Try open chrome to go live on Facebook and copy the API key.
2: Second Laptop: Go to OBS stream settings lets say Facebook and hit to paste the key.
3: Start streaming on OBS on 2nd laptop
4: Go to first laptop and hit GO LIVE from Facebook Live page.
5: This worked for me, hope will work and help some people.
 
You must log in or register to reply here.
Top