OBS Crashing Randomly with Streamer.Bot Intergration

UnicornsDreams

New Member
Hello,

I'm having an issue that very randomly and sporadically, whether streaming or just testing stuff off-stream, that when an action is done by Streamer.Bot that OBS crashes. I have spoken with their support but has been limited so I'm hoping it's possibly an OBS side issue that someone might spot with maybe too much going on or incorrect setting within OBS. Any help is super appreciated thank you.

Log of one example when I've been testing actions off-stream and OBS crashed - https://obsproject.com/logs/SVtkZ9P-J2QtpWL3
 

PaiSand

Active Member
You're using SE.live plugin. Please contact them for support.
Alternatively, uninstall it. Then uninstall and reinstall OBS in order to fix the changes made by this plugin. Now please do a test stream/recording of more than 30 seconds and post the log file here.
 

PaiSand

Active Member
You have only a few minor issues not related to the bot ocurrence.

If the bot is sending a code which kills OBS, then don't use it.
Also, this errors:
00:31:59.942: Source ID 'motion-filter' not found
00:31:59.942: Failed to create source 'Zoom Face'!
00:31:59.942: Source ID 'motion-filter' not found
00:31:59.942: Failed to create source 'Zoom VRM'!
00:31:59.942: Source ID 'motion-filter' not found
00:31:59.942: Failed to create source 'Zoom Scan Face'!
00:31:59.942: Source ID 'motion-filter' not found
00:31:59.942: Failed to create source 'Zoom Scan VRM'!

We need more info about the bot and which actions are performed and how you integrrated it.
 

UnicornsDreams

New Member
The errors probably relate to a couple of filter addons I had.

The connection is via the OBS Websocket plugin, it grabs various API calls from Twitch for various actions (Hosts, Raids, Follows, Subscriptions, Bit Cheers etc) and typically involves a GDI Text Change and Visibility State changes for text/images in OBS for these actions. Not sure if that's the sort of information you was needing.
 

PaiSand

Active Member
Well, according to the crash report it's an issue on the browser source, most probably the alerts you are using.
Test one by one untill you hit the one causing the crash and check what this one does.
 
Top