OBS Stops Responding Mid-Stream

[TriggerRedd]

Hello,

My stream last night was absolutely plagued by OBS entering an unresponsive state and requiring me to force close the program. The interval was seemingly pretty random, from a few minutes to as much as 30. I ultimately had to give up on my stream, it was painful. I don't think it generated any crash logs, but I've attached a few of the main logs.

Couple thoughts/potential causes from my end...

All three of these logs end with multiple sequential hits of:
warning: Could not update timestamps for discarded samples.
I don't know what this means, but is this some kind of rapid-fire command that OBS just isn't able to process, hence the hang?

I also updated MixItUp, (which I run while streaming) Windows, and OBS to 28, like a fool, and now it's pretty hard to determine whether or not these new versions are playing nice with each other. Probably another reasonable cause.

I ran two of the attached logs through the log analyzer but it didn't return anything critical.

Would super appreciate any help, short of burning it all down and trying from scratch I just don't know where to go from here.

 

[TriggerRedd]

Continuing to do some research, I'll note a few more things I've found, but ultimately no solutions.

1) I don't have to be live for this unresponsive state to occur. It's happening in OBS at intervals I can't pin down and there is no commonality except the deluge of "could not update timestamps for discarded sample" strings. I think sometimes they fry OBS, sometimes they don't.
2) All of the hangs occur after it fails to "apply a style" from this random "Hellt" github, but boy do I not know who this is. Is there a way to tell why it's trying to access this or what part of my content is doing so? The log calls the source "localhost:8111/overlay/:0" which doesn't tell my eyes much.
3) I have several commands tied to my redeems that trigger a browser source based HTML script that plays random WebM, mov, or MP3 files. Digging further, it seems the "could not update timestamps" thing might be tied to that, but... hard to say.

I posted it on the discord but didn't get much there, I'm sure this is a complex issue and ya'll are volunteers besides. I appreciate any and help!

 

[TriggerRedd]

Okay, deleted literally everything and I've started re-doing all my scenes and media from scratch, paying special note on the logs as I do. Interestingly, I started getting the "could not update timestamps for discard samples" as soon as I got my camera borders in, which are .webm files with some transparency in them. I think it potentially aligns with some of the stuff being discussed in this bug report from the OBS Mantis database back in 2017: https://obsproject.com/mantis/view.php?id=942

That said, OBS has been stable for an hour plus. I don't think the flood of this message is actually what caused the problem and it was probably the failing to apply a style thing from whatever's attempting to access this random github. At this point I'm just keeping ya'll updated since maybe someone, someday, will need it... heh

 

[TriggerRedd]

The saga continues, I was 90% sure it was MixItUp, a third party tool, causing the hang. localhost:811 is in fact MiU, and they're the ones trying to access that github that isn't playing nice with OBS. I've gone to ask them about it in their discord, though, and wouldn't you know it, in the fresh install, all the MIU commands are working, it hasn't hung at all. As soon I import scenes from my old install though, the hang comes with it. This is truly a journey

 

[TriggerRedd]

ALLL right narrowing things down even further - as I suspected, the deluge of warning: Could not update timestamps for discarded samples. is probably being caused by my web cam border, a looping .webm file with transparency that I got from streamspell. I watched the log in real time and a new line of this appears every time it loops.

But I'd had that forever! Which means... if the deluge of those strings nor the failure to apply the style is causing the hang.... WHAT IS

Perhaps I just flew too close to the sun. I only have 32GB of ram, and all my scenes, animations, text, plus an alternate scene collection with more of that just led to OBS proverbially pooping the bed. I may never know the truth of this, and I'm slowly coming to accept it. Thank you for reading all this if you have been, though I've been alone, it's been cathartic to post about it.

 

[Euphrane]

ALLL right narrowing things down even further - as I suspected, the deluge of warning: Could not update timestamps for discarded samples. is probably being caused by my web cam border, a looping .webm file with transparency that I got from streamspell. I watched the log in real time and a new line of this appears every time it loops.

But I'd had that forever! Which means... if the deluge of those strings nor the failure to apply the style is causing the hang.... WHAT IS

Perhaps I just flew too close to the sun. I only have 32GB of ram, and all my scenes, animations, text, plus an alternate scene collection with more of that just led to OBS proverbially pooping the bed. I may never know the truth of this, and I'm slowly coming to accept it. Thank you for reading all this if you have been, though I've been alone, it's been cathartic to post about it.

Did removing the web border do anything? And if anything, did you find a solution? I read your journey and appreciate that you at least attempted and updated along the way. I am also having this trouble. I'm assuming its my overlays at this point but can't figure it out.