Browser Element (Using StreamElements) Causes Memory Leak Mac Os 10.15.7

mr_joe

New Member
Firstly, I'm aware OBS does NOT work on Big Sur, this error occurs on Catalina.

It's very easy to reproduce. Simply create a browser elements with some stream elements theme. Then watch your memory usage go up, refer to my screenshot to use activity viewer on the memory section. You don't need to be streaming for it to go up. Simply having it 'active' will cause this to occur.

Furthermore, if you 'hide' the element by making it not visible ALL the memory is freed again. So as a horrible workaround for now for streamers ... to free your memory you may have to disable stream elements for a bit by hiding it in OBS to clear the memory (takes about 3 - 7 seconds) and then put it back on to prevent the out of memory errors.

This tells me the error is with the browser source right now. Being a developer and streamer myself I would be more then happy to look into this if someone would be so kind as to point me in the right direction to get started.

Thanks in advance!
 

Attachments

J3ster

New Member
Hey mate, I registered just so I could give you a possible solution as I was having this issue as well.

After some testing, I've found it to be when you set the text to scroll for your latest subscribers / followers etc. When you set them to static the problems doesn't appear to happen with the memory spike.

I'd be curious to see if your issue is due to the same elements.
 

mr_joe

New Member
Thanks J3ster I was starting to think no one cared =(. So you are saying that any browser element I use if it has a text that can scroll this is what is causing the issue? Can you define a bit more what that means with some examples?
 

J3ster

New Member
In your streamelements overlay, if you have an element; say for example 'Latest followers' and in the text option for the element, if 'text scrolling' is turned on, that is when I get the memory issues. I've added a picture of the options panel.

Let me know if you want me to expand further.

I'm not sure if its an OBS issue or streamelements... =\

Screen Shot 2020-12-24 at 8.11.53 am.png
 
Top