Question / Help OBS Studio cef-bootstrap (Browser Source?) RAM use.

[Rhyfel]

Been trying to figure something out, there are 2 "cef-bootstrap.exe" processes running on OBS Studio (They come from the plugin folder). While obs studio is running (Not necessarily streaming, just running) both processes increase on their RAM usage slowly. I searched and some people have reported the same thing. Replies seem to indicate that this can be a normal thing depending on what you put on your browser source, how ever: It's just streamlab's notifications thing, and both bootstrap.exe's KEEP INCREASING for some reason.

While streaming something like Dark Souls III it starts being a bit of an issue since DS3 uses quite a bit of RAM too, so I end up having to restart OBS after an hour or so. Restarting OBS brings the processes back to their normal RAM values, increasing slowly once again.

A few notes.

Using 32bit or 64bit seems to make no difference.

This is not as much of an issue when streaming some lighter game, I can't recall if they ever STOP increasing RAM usage or if it's just not noticeable since the game had lighter RAM usage.

I only have one Browser Source enabled on this scene, and one in another. Why are there 2 cef-bootstraps? Does it run on the other scene even when you have another scene active? Why are both increasing. And why would the browser plugin for streamlab's notifications do such a thing (increase RAM like that).

I do have other browser plugins that are currently disabled (The eye icon is crossed out) on other scenes, and other cef-bootstrap processes running but they don't increase RAM, so I would assume they belong to the disabled sources right.

The cef-bootstrap processes were both at something like 34.000K RAM (Task manager) when I checked while writing this post. They are now at both 270.500K RAM or so. Still increasing.

At some point they both individually use more RAM than obs itself.

Having Preview disabled doesn't stop them from increasing their RAM use.

I am running NVENC H.264 encoder cause I heard it's good for Nvidia, not sure if that is related at all to cef-bootstrap or how much RAM they use, but it's like one of the only major things I messed with on OBS.

 

[c3r1c3]

1. Each unique Browser Source instance creates a CEF.
2. Using 64-bit OBS can help (assuming you have enough RAM) if only because it'll take longer for the issue to show up. If you have 4 Gigabytes of RAM or less, then you should stick to the 32-bit OBS.
3. Has nothing to do with NVENC.
4. If you run Chrome, you'll notice it tends to do the same thing. Why? Because CEF (for all intents and purposes) *is* Chrome.
5. While it's a slim chance it's a bug in OBS, it's most likely (I would say 99% chance of) Chrome being Chrome, so it's unknown when/if the issue can or will be fixed.

 

[Rhyfel]

1. Each unique Browser Source instance creates a CEF.
2. Using 64-bit OBS can help (assuming you have enough RAM) if only because it'll take longer for the issue to show up. If you have 4 Gigabytes of RAM or less, then you should stick to the 32-bit OBS.
3. Has nothing to do with NVENC.
4. If you run Chrome, you'll notice it tends to do the same thing. Why? Because CEF (for all intents and purposes) *is* Chrome.
5. While it's a slim chance it's a bug in OBS, it's most likely (I would say 99% chance of) Chrome being Chrome, so it's unknown when/if the issue can or will be fixed.

I see, thank you.

EDIT: Figured it out, it wasn't Streamlabs indeed. The 2 disabled Browser Sources from Discord were still recording the discord chat (despite being disabled) and as such OBS was running them. They were the processes in question.