I have no idea how to read crash logs

Yeah, those are pretty cryptic. It's a record of *exactly* what was in memory at the time, so that someone who really knows the software can wonder how in the world *that* value got *there*. I create those things myself for my software projects, and it really does take an intimate knowledge of how the code works (or is supposed to work) to make sense of it. But when you have that, it's quite useful.

It would also be good to post a normal logfile. They're much more readable, and might have a good clue before it ends abruptly. Maybe a loading or error message from a badly-written plugin, for example. Remove that plugin (and figure out how work without it), and you might be good. Then report the crash, with documentation, to that plugin's thread here.
 
Yeah, those are pretty cryptic. It's a record of *exactly* what was in memory at the time, so that someone who really knows the software can wonder how in the world *that* value got *there*. I create those things myself for my software projects, and it really does take an intimate knowledge of how the code works (or is supposed to work) to make sense of it. But when you have that, it's quite useful.

It would also be good to post a normal logfile. They're much more readable, and might have a good clue before it ends abruptly. Maybe a loading or error message from a badly-written plugin, for example. Remove that plugin (and figure out how work without it), and you might be good. Then report the crash, with documentation, to that plugin's thread here.
i can post the log reports but i have 8 from that day trynna stream and multiple crashes and dont know which one/ ones to post
 
i just updated a couple of my drivers just incase that may have been part of the issue, have yet to try and stream since saturday. i also decreased my bitrate from 2500 to 2k after i ended saturday
 

Attachments

I saw them. I was just waiting for someone who knew better to see them too. Since there hasn't been yet, I skimmed through them to see if anything jumped out at me. Nothing did, except you have a lot of these, that make it hard to see anything else:
12:54:09.476: (https://streamelements.com/overlay/...FCcZ67Z6Y1CSC-t_M7okJzsHOkZf4i12hp0wx8YLHx:62)
12:54:09.476: [obs-browser: 'ending'] Error: [Report Only] Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'none'". Either the 'unsafe-inline' keyword, a hash
Since you have a lot of those, that won't be what's causing the crash. So I ran them all through our Automatic Analyzer to see what it would come up with:
This one is probably the best summary:
1686861487260.png

Sometimes plugins are buggy, and can cause OBS to crash. Don't know if that one does or not, and there's not a good way for the Analyzer to tell either.
 
Back
Top