Browser source stops updating after a while

DidierMalenfant

New Member
I filed a bug report yesterday which unfortunately got, I believe, incorrectly shut down.

I have a browser source pointing to a stream lab chatbox. After a while, sometimes a few seconds, the source stops updating and needs to be refreshed in order to work again.

I open a Firefox windows using the same URL for the chatbox and that window continues to update correctly throughout.

Am I right in suspecting the problem comes from OBS? Any suggestions as to what steps I can take to diagnose this further?

I'm on macOS 15 with OBS 30.2.3 on an M2 MacBook.
 

DidierMalenfant

New Member
Tried using Safari with the URL and the result is the same as with Firefox. It works.

Also found this where one poster is also very dismissive about this potentially coming from OBS but one fix in that case seems to involve OBS.

I opened a support ticket with StreamLabs too but it does look odd that two browsers handle the source correctly and OBS isn't.

Just to be clear, I'm not trying to lay the blame anywhere. Software is hard, bugs happen and OBS is an amazing piece of software written and maintained by very talented people.
 

DidierMalenfant

New Member
Further info, I seem to be able to repro the issue with Twitch alerts too. Those URLs don't come from StreamLabs but directly from Twitch.

Same symptoms. Browser source works, eventually stops updating correctly (sometimes after just a few seconds, sometimes more, can't figure out the rational there) until you refresh the cache on the browser source. Then OBS picks up the updates again until it doesn't.

So it could be an issue with my setup, a user error on my end or something to do with the way OBS deals with URL that update but I don't think it's limited to just StreamLabs.

Just trying to figure this out.
 

WizardCM

Forum Moderator
Community Helper
When this occurs, do other browser sources or docks stop working too?

As a note, OBS doesn't do anything special with how pages update, it's just an embedded Chrome instance. While there are occasionally things that misbehave due to us currently using an older Chrome (103), it's often caused by something else.
 

DidierMalenfant

New Member
Good point. I tried adding another source pointing to an online clock. That one keeps on working no problem.

I don't have Chrome on my computer so I can't compare with that. The way I see it it's either:
  • Something different on my computer (maybe since the macOS 15 update?). I tried disabling LittleSnitch and the Apple Private Relay just to be sure.
  • Something with StreamLabs. I opened a ticket with them, no reply yet. But even my Twitch alerts are flaky, although that could be totally unrelated.
  • Something with the way OBS handles this. I've seen older reports where this issue was fixed by deleting the browser cache folder on Window. I'm on macOS but deleting that folder in Application Support doesn't seem to help. It's like refreshing there source, it works again for a while but eventually fails again.
Thank you for the help! In the meantime I've put together a temporary work around.
 
Top