OBS Crashed during livestream

[WarFiff]

Hello all,

This is a cross-post with the window-support discord channel. I'm not sure if that is allowed, and if it is not, please let me know and this thread can be deleted.

I've been having some issues with OBS crashing after around 1 hour or so of streaming. I've uploaded the crash report here: https://obsproject.com/logs/3KktMFrXEDBdjz4O. Here was the log file from the time of the crash: https://obsproject.com/logs/VwAD4QrvCDE3RPzc, though the crash happened at 10:50am and the log file only goes out to 10:17am.
I've tried to read through posts, comments, and make configuration changes, but so far have not had much luck finding a solution to my issue. If I'm posting this incorrectly or something else needs to be shared please let me know.

Thank you all.

 

[WarFiff]

Okay, so I may have tracked this down. Leading up to the crash I saw the following two messages in the System Event Log:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: obs64.exe (10384) consumed 631357440 bytes, MBAMService.exe (4632) consumed 362209280 bytes, and chrome.exe (11984) consumed 317681664 bytes.

Followed by:

Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.

My system was configured to "Automatically manage paging file size for all drives. And it had the available size set to something like 2456 MB (I didn't capture this before I made a change and should have).

From what I can find online, Microsoft recommends the initial value to be 1.5 times your RAM available and I saw some suggestions for max value set at around 3 times your RAM.

I will say that this seems a bit excessive, but for my system with 16 GB of RAM, that would run at 24576 MB - 49152 MB, which sets the initial size at around 10x what Windows was allocating when it was managing it.

I will try again with these settings (though I'm a little weary of performance offloading so much memory to disk, even with an SSD).

Any Windows gurus out that that have any suggestions of what this should be set at or if what I'm trying is going to cause future headaches with degrading performance, please let me know your thoughts.

 

[WarFiff]

I'm actually going to set it back to system managed for now (looks like that drops me back to 2432 MB of virtual memory, so I was close with my 2456 MB guess).

After looking around, I'm a little hesitant to set more virtual memory on an SSD as constant reading/writing from SSD can cause them to wear out much quicker.

It seems like there may be a memory leak somewhere. As having OBS, chrome, and MBAM protection running shouldn't eat up 16 GB of memory (MBAM wasn't running a scan at the time, just real-time protection). I'm only capturing from a video capture device and several ASIO4ALL audio channels.

I know that the log mentioned that my audio sample rate wasn't matching some of my devices. I wouldn't think that would cause a memory leak, but I guess I don't know for sure. I will try updating that as well and do some more testing.

I will be back with a report, if I can pinpoint what is eating up the memory and causing this crash to occur.

 

[WarFiff]

So one more report before I call it a night. I was able to confirm that while OBS was running the virtual memory continued to climb. With just Chrome running it jumps up, but plateaus. Somethings up with my OBS instance. I do have an asio plug in added to support asio4all inputs, which could be part of it too.

I'm going to downgrade to an older version of OBS and the asio plug in to see if that makes any difference.

I'll report back findings.

 

[WarFiff]

Well, it looks like I'm talking too myself here, but just in case someone else runs into the same crash scenario, my experience may inspire some things to try.

I'm not positive on the exact fix, as I made a few changes while testing. The above errors appeared to be signs of a memory leak of some kind, so I figured I should at least reinstall most of my software. I ended up leaving my system settings alone (letting widows manage my memory paging).

I ditched asio4all for the one provided by behringer for the xr18. It seems to have a higher latency, but otherwise seems to work alright. I also installed OBS 26.1.1 then updated through the app to 27.0.1. And I reinstalled the OBS ASIO plugin (from Andersama's github) for OBS 27. One last thing I did was update the firmware on our xr18.

I was able to hook up to a stream and it didn't crash after 3 hours of running. The virtual memory also stayed around the 20-30% committed during the stream. No more gradual growth. I think I'm in the clear of the errors.

If I had to guess it was something not playing nicely between the asio driver I was using, the asio plugin, and obs, but I wasn't really able to nail it down.

 

[Neiloch]

Googled this problem and found this thread. I just started having this problem with OBS after the last update and I'm not sure why. OBS is forcing full use of my page file to the point of completely using up my drive and windows prompting me to 'free up space.'

 

[Neiloch]

Last night it happened again, OBS crashed outright, I relaunch and it gives me an error about the stream key being unavailable (?) likely from the sudden disconnect. (Sorry I'm not sure what message it was, I was in a panic to restart the stream so I just changed my destination server and it worked.)

Then later it filled up the page file again, I monitored this by simply having my drive listing up showing their free space. When it filled up again OBS:

1. Froze
2. Twitch docks became blank, black boxes
3. OBS unfroze
4. Twitch docks reappeared
5. Stream continued normally

The drive was back to the normal amount of free space, seemingly clearing the page file outright.

 

[Neiloch]

SOLVED: I turned off hardware acceleration for web sources and the filling of my page file stopped. It was occurring just by having OBS open so that told me it wasn't because of streaming. I'm not sure why that was such an issue suddenly in the past few weeks but its not longer causing that problem, at least.