Bug Report 3am Crash and Scheduling Request

[southlegend]

Hi all.

So I'm currently responsible for the tech installation of the live streaming function of a public broadcasting system in my city.

As it's a non-profit organisation and there is a non-existent budget, I've been working on ways to get reliable streaming to cover our broadcasting hours 7am-11pm every day.

At the moment I'm using OBS Studio with a HD PVR 2 to stream to a private rtmp server, which works really well! Well done on the software, it's crazy that this is free!

The only issue I'm having is that because there is no auto-stream schedule function in OBS, it's being left to stream 24 hours a day. Now it does this just fine until 3am every morning.

Each crash log shows the following:

Unhandled exception: c0000005
Fault address: 7FEF7F2C4E8 (c:\windows\system32\msvcr120.dll)

The msvcr120.dll file points me to the Visual Studio runtimes, which I've reinstalled (both x86 and x64) and hasn't made a difference.

The crash logs are exactly the same (http://d.pr/f/1fsc6) and they all happen within 20 seconds of the clock turning 3:00am.

Now last night I tested leaving OBS open and previewing the input but without streaming, and it has survived the night with no problem.

Is there a way to schedule the streaming that I'm not aware of? As I only need it from 7am to 11pm and this would avoid the 3am crash.


Finally, I've seen that there was an autostart on streaming in the old OBS via a shortcut argument. Does this still exist in OBS Studio? I've tried the old suggestions but they don't seem to work.


Thanks for your time!

 

[c3r1c3]

I think the commandline parameters haven't been added back yet.

I've been testing OBS Studio for 24/7 streaming and 5 days into (0.14.1), it's holding up as well as OBS classic (i.e. worked for 2+ weeks without needing to restart or reboot). That would lead me to think it's something local on your machine. Could be something like a process set to run at 3am. Maybe an Antivirus scan, or a disk defrag job, and that's causing OBS to crash.

 

[Xphome]

That's an interesting issue, how many times has it crashed around 3 AM? And was the stream started round the same time (so that the duration was about the same for all the sessions that crashed)?

About autostart streaming, this was added in 0.14.0:

Added command line parameters: --collection [scene collection name], --profile [profile name], --scene [scene name], --startstreaming, --startrecording. If a collection/profile/scene has a space in the name, use quotes around the full name.

 

[southlegend]

I think the commandline parameters haven't been added back yet.

I've been testing OBS Studio for 24/7 streaming and 5 days into (0.14.1), it's holding up as well as OBS classic (i.e. worked for 2+ weeks without needing to restart or reboot). That would lead me to think it's something local on your machine. Could be something like a process set to run at 3am. Maybe an Antivirus scan, or a disk defrag job, and that's causing OBS to crash.

Glad someone is having success with 24/7 streaming! I don't think our HD PVR 2 works well with OBS Classic so I can't test that.

I checked the antivirus and you might be on to something there. We have McAfee which is managed remotely by our system admins so I can't change any settings without their say so (highly unlikely they'll do it!). I checked the logs and it seems that there was a scan triggered this morning at 3am... I'm gonna leave the streaming on tonight and see if there's a scan on tomorrow morning to coincide.

I did just force a scan though and the streaming survived through that, so I'm not 100% certain that's the issue.

The only other thing I could see in Task Scheduler is that Microsoft Compatibility Appraiser is set to be triggered every day at 3am. Seems unlikely, but I've disabled it anyway.

Thanks for your suggestions!

That's an interesting issue, how many times has it crashed around 3 AM? And was the stream started round the same time (so that the duration was about the same for all the sessions that crashed)?

About autostart streaming, this was added in 0.14.0:

Added command line parameters: --collection [scene collection name], --profile [profile name], --scene [scene name], --startstreaming, --startrecording. If a collection/profile/scene has a space in the name, use quotes around the full name.

For the three days I've done the streaming, it's crashed each morning. There doesn't seem to be a correlation between the stream length as I've started the streaming at times between 9am and 5pm.

Thanks for those parameters - the --startstreaming worked first time!

 

[southlegend]

Just as a follow-up to my issue...

I ended up creating some scripts using AutoHotKey that send a keypress to OBS when they are run. I've setup HotKeys in OBS for starting and stopping the stream.

The two scripts I've created basically send keypresses to trigger those HotKeys and it works! I compiled the scripts into executable files and have them setup in Windows Task Scheduler for automation.

It's not a fix to the issue I'm having, but it gets around the problem.

Thanks c3r1c3 and Xphome for the help.

 

[The Show Sarnia]

Are these scripts available somewhere?

Thx