Version 4 (x64) crashes - reproducable

[nstig8]

I upgraded to Version 4 (64 bit) and have had intermittent Blue Iris crashes ever since. I changed it to run as a Windows service so that it would re-launch itself after a crash and that has been "good enough" to not go back to v3. However, tonight I was upgrading the firmware on my 3 Foscams and changing recording settings, and I was able to consistently reproduce the crashes.

I have a couple 3MP hikvisions hooked up direct-to-disk and my 3 640x480 Foscams have been set up as mp4 reencode to get the Blue Iris timestamp overlay. Tonight I switched them to direct-to-disk while I was messing around and I was able to consistently and easily get BlueIris.exe to crash just by moving the cameras around outside BI (directly via their own web interfaces) to trigger motion alert recordings. I think it has to do with the poor connection/fps of the Foscams while direct-to-disk recording. Two of these cameras are connected via wifi and bounce around at roughly 8fps. They cause consistent crashes of BlueIris.exe during direct-to-disk recording and NOT during re-encoded recording. My hard-wired Foscam does not cause the crashes during direct-to-disk recording.

My PC is an i5 with 16GB of RAM and never goes above 25% CPU utilization running BI.

Anyone with insight on how I can get better log output so I can give some more meaningful insight into the problem please let me know. Thanks.

Here is my BlueIris log of some of the crashes:
3 1/21/2015 9:42:09 PM nursery MOTION
2 1/21/2015 9:42:12 PM App Restarted after unexpected shutdown
4 1/21/2015 9:42:13 PM Clips C:: 1197, 16.5G/30.7G (+59.5G)
4 1/21/2015 9:42:13 PM Clips \\FREENAS: 3687, 47.4G/100.0G (+61.0G)
0 1/21/2015 9:42:13 PM Server Started on port 11110
0 1/21/2015 9:42:14 PM App Today's sunrise: 7:25 AM, sunset: 5:17 PM
3 1/21/2015 9:42:15 PM nursery MOTION
2 1/21/2015 9:42:18 PM App Restarted after unexpected shutdown
4 1/21/2015 9:42:19 PM Clips C:: 1198, 16.5G/30.7G (+59.5G)
4 1/21/2015 9:42:19 PM Clips \\FREENAS: 3687, 47.4G/100.0G (+61.0G)
0 1/21/2015 9:42:19 PM Server Started on port 11110
0 1/21/2015 9:42:20 PM App Today's sunrise: 7:25 AM, sunset: 5:17 PM
3 1/21/2015 9:42:22 PM nursery MOTION
2 1/21/2015 9:42:24 PM App Restarted after unexpected shutdown
4 1/21/2015 9:42:25 PM Clips C:: 1199, 16.5G/30.7G (+59.5G)
4 1/21/2015 9:42:25 PM Clips \\FREENAS: 3687, 47.4G/100.0G (+61.0G)
0 1/21/2015 9:42:25 PM Server Started on port 11110
0 1/21/2015 9:42:26 PM App Today's sunrise: 7:25 AM, sunset: 5:17 PM
3 1/21/2015 9:42:28 PM nursery MOTION
2 1/21/2015 9:42:30 PM App Restarted after unexpected shutdown
4 1/21/2015 9:42:31 PM Clips C:: 1200, 16.5G/30.7G (+59.5G)
4 1/21/2015 9:42:31 PM Clips \\FREENAS: 3687, 47.4G/100.0G (+61.0G)
0 1/21/2015 9:42:31 PM Server Started on port 11110
0 1/21/2015 9:42:32 PM App Today's sunrise: 7:25 AM, sunset: 5:17 PM
3 1/21/2015 9:42:33 PM nursery MOTION
2 1/21/2015 9:42:36 PM App Restarted after unexpected shutdown
4 1/21/2015 9:42:37 PM Clips C:: 1201, 16.5G/30.7G (+59.5G)
4 1/21/2015 9:42:37 PM Clips \\FREENAS: 3687, 47.4G/100.0G (+61.0G)
0 1/21/2015 9:42:37 PM Server Started on port 11110
0 1/21/2015 9:42:38 PM App Today's sunrise: 7:25 AM, sunset: 5:17 PM
3 1/21/2015 9:43:04 PM nursery MOTION
2 1/21/2015 9:43:07 PM App Restarted after unexpected shutdown
4 1/21/2015 9:43:08 PM Clips C:: 1202, 16.5G/30.7G (+59.5G)
4 1/21/2015 9:43:08 PM Clips \\FREENAS: 3687, 47.4G/100.0G (+61.0G)
0 1/21/2015 9:43:08 PM Server Started on port 11110
0 1/21/2015 9:43:09 PM App Today's sunrise: 7:25 AM, sunset: 5:17 PM


Here is my Windows Event log from one of the crashes:
Faulting application name: BlueIris.exe, version: 4.0.0.23, time stamp: 0x54bdaa79
Faulting module name: BlueIris.exe, version: 4.0.0.23, time stamp: 0x54bdaa79
Exception code: 0xc0000005
Fault offset: 0x00000000005eac06
Faulting process id: 0x126c
Faulting application start time: 0x01d035f2f849fd56
Faulting application path: C:\Program Files\Blue Iris 4\BlueIris.exe
Faulting module path: C:\Program Files\Blue Iris 4\BlueIris.exe
Report Id: 38b4a68b-a1e6-11e4-bebb-80ee7336fe01
Faulting package full name:
Faulting package-relative application ID:

 

[nstig8]

Also, every time it crashes I get a 0 second, 0 size video clip in the clip viewer with the red rectangle around it that never goes away. I can't play the clip in BI because it thinks the mp4 is still recording, when in fact the application has already crashed and been restarted by the windows service watchdog.

 

[fenderman]

Welcome to the forum. I would email support and see what he says..in the interim see if recording to BVR instead of mp4 stops the crashes..

 

[Zxel]

I have this exact same problem with the exception of I am using the native BI .bvr format. Constant crashes by BI (BI Tools handles the crashes - no need for service mode), all with very little in the BI log to indicate why, the only thing that is consistent is a camera will have a connection issue right before the crash. I have one wireless camera in my system (an inexpensive hootoo from way back) and it is normal for it to lose connection or reset itself once in a while (although after several years of usage the under $50 it cost was well worth it). BI 3.x never had any issue with it or any other camera disconnect or network issue (even ones I created myself), it just showed the error message and followed the watchdog rules - as it should.

Now version 4.x (I am always at the current rev - 4.0.0.23 x64 as of this writing) will not always crash on a network issue, but when it does crash there always is a network issue right before it. The only other thing I have noticed (I really haven't been on top of this issue - BI Tools is allowing me to take a wait and see position) is this constant error in the windows event viewer when a crash happens (notice it's the same as yours):

Faulting application name: blueiris.exe, version: 4.0.0.23, time stamp: 0x54bdaa79
Faulting module name: blueiris.exe, version: 4.0.0.23, time stamp: 0x54bdaa79
Exception code: 0xc0000005
Fault offset: 0x00000000003be803
Faulting process id: 0x4cac
Faulting application start time: 0x01d0359950668f19
Faulting application path: C:\Program Files\Blue Iris 4\blueiris.exe
Faulting module path: C:\Program Files\Blue Iris 4\blueiris.exe
Report Id: b1b13d4d-a1be-11e4-aaf9-000272c69f99

It is always a 0xc0000005 exception error which I think may be related to the Microsoft Visual C++ Redistributable Package installation, however, it could be several other things also -duno I've been lazy. :sad2:

You may want to try and re-installing the Microsoft Visual C++ Redistributable Package needed for BI. also I read somewhere here on the forum that BI may have a problem with the 64 bit version of the package conflicting with the 32bit version of this package, once again I haven't been actively trying to peg and correct the problem. You could probably search the forum (using the search tool) and find the thread about it here easily enough - not like there is that many threads on BI 4 yet.

Hope that helps, anything else I can do to help you find the issue just ask.

 

[nstig8]

Okay, I sent my info off as-is. I'll post back if I get any type of a reply.

 

[Zxel]

Just posting this to further the find to the fix, take a look at this thread post, BI is corrupting the Db when it crashes, soooo make sure you rebuild your Db (right click on any clip in the clip list and select database/rebuild) after your BI crashes, then restart BI. This will fix the 0 second file and move/delete issues.

Now all we have to do is fix the crashing issue. Since some people report that BI 4.x is perfectly stable for them looks like an upgrade issue. I didn't want to have to hunt this issue down but now it looks like I will have to (poo!). I'll start by doing the easy stuff first to see if I can correct it without installing BI 4.x clean, I'll report back any headway.

 

[nstig8]

Ken emailed me today to ask for access to one of the cameras that causes my crashes. I gave him access and also included Zxel's better description of when the crashes occur. I also gave him the link to this thread. Hopefully he is able to figure out the root cause and fix it.

 

[Brian Mackenzie Mack]

i performed an update to 0.23 yesterday to see if it solved any issues constant crashes and i left it to run its course and it ran ok for the night and a bit of the mornning and then i went to check into it today from work and lo and behole nothing it had fallen flat on its face AGAIN!!! this is nuts i pay for it and still dose this so its back to bi 3 till it is fixed. i have had no issues with 3 what is wrong with the new software

 

[Zxel]

i performed an update to 0.23 yesterday to see if it solved any issues constant crashes and i left it to run its course and it ran ok for the night and a bit of the mornning and then i went to check into it today from work and lo and behole nothing it had fallen flat on its face AGAIN!!! this is nuts i pay for it and still dose this so its back to bi 3 till it is fixed. i have had no issues with 3 what is wrong with the new software

Try installing the 64bit version of Microsoft Visual C++ Redistributable Packages for Visual Studio 2013, so far since installing it I haven't had a BI crash (but is hasn't been long enough yet for me to declare it a fix).

I got the idea from this post.

 

[fenderman]

i performed an update to 0.23 yesterday to see if it solved any issues constant crashes and i left it to run its course and it ran ok for the night and a bit of the mornning and then i went to check into it today from work and lo and behole nothing it had fallen flat on its face AGAIN!!! this is nuts i pay for it and still dose this so its back to bi 3 till it is fixed. i have had no issues with 3 what is wrong with the new software

The new software is recompiled in 64 bit..so maybe there is something going on there. Have you tried running 32 bit? Have you emailed the developer with your crash info? It is impossible to fix something he does not know about.... Without more information about your crash there is know way to know what is causing it...

 

[nstig8]

Try installing the 64bit version of Microsoft Visual C++ Redistributable Packages for Visual Studio 2013, so far since installing it I haven't had a BI crash (but is hasn't been long enough yet for me to declare it a fix).

Just installed the 64 bit C++ files and restarted my Blue Iris service. I will find out if it works or not when I put my son to bed in a few minutes. BI was crashing like crazy while my wife put the baby to bed. Those are the two rooms with the wifi Foscams that give me issues. I have BI set up to push notifications to my phone when it crashes, so I will know right away.

Also it is still crashing for me even with direct-to-disk turned off, so that was just a red-herring from when I happened to notice all the crashes. My hard-wired cameras never cause a crash when they record (and one is the same model Foscam). It must be an issue with the network event code like Zxel was thinking.

 

[nstig8]

No crashes after an hour of bedtime routine stuff. You may have solved it with the 64 bit C++ Redistributable idea. If it doesn't crash in the morning when both cameras are in color mode I'll consider it fixed and let Ken know.

 

[Zxel]

No crashes after an hour of bedtime routine stuff. You may have solved it with the 64 bit C++ Redistributable idea. If it doesn't crash in the morning when both cameras are in color mode I'll consider it fixed and let Ken know.

Mine hasn't crashed either since doing it (still not long enough for the warm fuzzy feeling) - fingers crossed.

 

[nstig8]

Unfortunately there were two more crashes tonight when the baby woke up for her midnight feeding. Oh well. The light was on so maybe the additional bandwidth was enough to cause it. Each crash left a 0kb file with a permanent red triangle around it in the "Clips" pane. The actual files on disk had sizes, but were unplayble in VLC. Same windows event viewer error as always.

 

[Zxel]

Rebuilding the BI Db (right click on any clip and select database-rebuild) will fix the file issues, make sure to restart BI afterwards.

I also had several crashes tonight - so still on the hunt for the solution. I've been told a clean install is one way to fix this issue, but I'd like to fix it without doing that, so I will do some more troubleshooting. If I cannot find it soon though I will perform a clean install and see if that fixes it.

P.S. As part of the clean install you are supposed to remove all traces of BI (all versions) - i.e. you cannot transfer the settings from an existing install - you must set up everything from scratch.

 

[nstig8]

Ken sent me an email that version 24 he is switching back to MP3 for audio rather than AAC. He thinks that will be more stable. It is very possible the audio is causing my crashes. My Foscams have audio and the other cameras do not.

 

[schaijik]

I have the same problems with version 23, I have 3 Foscam camera's with sound (of 5 in total). For now the sound is off to see if the crashes still occur.

 

[Zxel]

Ken sent me an email that version 24 he is switching back to MP3 for audio rather than AAC. He thinks that will be more stable. It is very possible the audio is causing my crashes. My Foscams have audio and the other cameras do not.

That is interesting because the network retry and timeouts I get right before a crash is coming from a HooToo camera which is a Foscam clone, so that makes sense to me. I supose I will try turning off the sound and see if that helps (or just disable that camera for now).

Thanks for the heads up!

 

[schaijik]

I have the same problems with version 23, I have 3 Foscam camera's with sound (of 5 in total). For now the sound is off to see if the crashes still occur.

14 hours of soundless running and no crashes yet.

 

[Zxel]

At first I just disabled the sound on my Hootoo (Foscam clone) and BI still crashed, however, after disabling the entire camera I have yet to get a crash (16 hours and counting). I'm going to wait some more before a declaration but I really do think this is it - BI has a problem with Foscam cameras.

On the lighter side that is sooooo funny - BI was designed for Foscam (If I have its history right). :laugh: