Bug with browser plugin and cache data (Stream Elements Kappagen overlay and Javascript Errors).

Sphynx

New Member
Hi there,
I'm not sure if this is the best place to post this but good enough to start.
I have been dealing with this issue extensively for a while now. I use Stream Elements kappagen as an overlay to show emotes on my stream and after having many issues and working with Stream Elements I've discovered this is specifically an issue with OBS' browser source plugin (and may be specific to my hardware or my scene setup, still unsure).

Problem:
After some period of usage of a browser source to display the kappagen overlay, the OBS browser source starts to not show certain emotes at all, and certain animated ones will not animate at all. If the overlay source is opened in any web browser (tested chrome, firefox, edge) all of the emotes display and animate properly, while in OBS they do not. The only temporary solution I have found is to go into the OBS appdata folder for plugin config/browser plugin and delete everything in the cache folders. Typically this will fix the issue for a short period of time, but it will start to happen again within anywhere from days to weeks.

Some other notes and troubleshooting:
I have a lot of emotes that are used in the overlay (343 between FFZ, BTTV, 7tv, and another 30 on twitch itself). I'm not sure if somehow the cache is being overloaded and data is being corrupted or what. I have done things like enabling/disabling hardware acceleration on the browser source, I have removed all OBS browser sources from all of my scenes (there is only actually one to begin with for the emotes), I have checked logs (nothing comes up related to the browser source). I have reinstalled OBS and tried different versions as well, the issue persists.

I know this isn't really a super important issue, but there is definitely something broken in the OBS browser source plugin and how it handles a Kappagen browser source specifically. Again might be due to the sheer number of emotes that I have, or it might be something related to my specific setup. But I was hoping to make the devs aware of it. I can provide any other info if necessary.

I have included two different logs, one before clearing the cache (8/4), and one after(8/5), (my scenes are messy, but I've also tested this on trimmed down scenes with only the essentials I need and it still occurs). There is a very clear difference and it appears like it is some javascript error that is happening when the browser plugin is attempting to access the Stream Elements overlay. I'm not really sure if there is anything I can do on my end to fix this other than repeatedly clearing the caches every week or two. Any help would be appreciated.
 

Attachments

  • 2023-08-05 20-03-24.txt
    91.6 KB · Views: 69
  • 2023-08-04 21-35-59.txt
    191.8 KB · Views: 34

Sphynx

New Member
just to clarify, about nothing coming up in the logs, i meant after clearing the cache. the logs clearly show that after a certain amount of time that the problem becomes noticeable that there are many js errors being thrown with the browser source
 

PaiSand

Active Member
Any issues related to third party apps and services must be asked to the support of that particular app / service.
If they deny the support, change the service.

Twitch has added alerts for twitch streamers, so you can use that too.
 

Sphynx

New Member
Perhaps you misread my post. I did go through stream elements support to verify it was not an issue on their end. The overlays display properly on every type of browser outside of OBS. Inside the OBS using browser source plugin (included in OBS, not 3rd party) they do not work correctly. Hypothetically I could just have the browser open and always be capturing that page and trying to key out things (which would not work great but doable), but why would I do that when we have the browser source for this exact function?
 
Top