Bug Report Memory leak (OBS 25.0.6 on Mojave)

[moertel]

OBS 25.0.6 on macOS Mojave 10.14.6. My current log file is at https://obsproject.com/logs/IUbMUlf5ghs4m7ER

I open OBS and without even starting to stream or doing anything, memory usage starts climbing from initially 1.5GB to 16GB and beyond. My system has 32GB total and I've seen it climb until my Mac effectively runs out of available RAM and starts swapping. Any idea what might be causing this?

And six minutes later we're at 14GB already...

 

[moertel]

Same thing with 25.0.7.

 

[moertel]

I started removing sources one by one. Removing my Streamlabs Tip Jar (added as a browser source) freed 15GB at once and memory usage is now stable at 3.2GB. (Adding it back in and boom, memory climbs again. Edit: No, wait, it did for a bit but is now stable again at 3.3GB, what the hell.) My other Streamlabs browser source is a text-only widget and seems to be behaving fine. So it seems that the image rendering could be the culprit.

Anyone else with a Streamlabs tip jar seeing this behaviour? (https://streamlabs.com/dashboard#/jar)
Any way to fix it?

 

[Narcogen]

Would start by removing all third party plugins.

 

[moertel]

@Narcogen I guess you've not read past my first post. ;) That's what I did and I identified a browser source (Streamlabs Tip Jar) as the cause. Is this something I need to raise with its creator? I do think OBS should handle this more gracefully though. Letting a browser source clog all available RAM seems like a bug.

 

[martinzuniga]

@moertel I'm having the same issue and have also narrowed it down to the various standard widgets I'm using, Tip Jar, Followers, etc. These are all very common widgets that can be seen on plenty other Twitch accounts. Have you found a solution? Thinking migrating to Streamlabs OBS is the only choice since these widgets are kind of important.

 

[Prate]

Same thing happening with OBS studio version 25.0.8-1 on Fedora 32 server.
My server running out of memory. I have to reboot server every alternate day
due to this issue.

Please fix this error with OBS or provide solution to fix this memory leak.