avcodec-53.dll crashing ispy.exe

[GoogleCodeExporter]

I've been using ispy for a couple of months and today I added more cameras. The 
system ran fine with 5 cameras but now I have 9 and it's crashing at least once 
an hour. I've made no other changes to the system. Here are the cameras I am 
using:

5x Vivotek IP8332
4x Vivotek FD8134

These cameras are connected to a Dell PowerConnect POE switch. The POE is 
connected directly to a Dell PowerEdge 2950 running Windows Server 2008 R2 
Standard Edition. I am running iSpy v4.5.4.0. Here are the crashes I am seeing 
in the Event Viewer:

Event ID: 1026
Source: .NET Runtime

Application: ispy.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at <Module>.avcodec_close(libffmpeg.AVCodecContext*)
   at AForge.Video.FFMPEG.VideoFileWriter.Close()
   at AForge.Video.FFMPEG.VideoFileWriter.Open(System.String, Int32, Int32, Boolean, AForge.Video.FFMPEG.VideoCodec, Int32, AForge.Video.FFMPEG.AudioCodec, Int32, Int32, Int32, Int32)
   at iSpyApplication.Controls.CameraWindow.Record()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

The event is immediately followed by:

Event ID: 1000
Source: Application Error

Faulting application name: ispy.exe, version: 4.5.4.0, time stamp: 0x50508096
Faulting module name: avcodec-53.dll, version: 0.0.0.0, time stamp: 0x4ed5c5b7
Exception code: 0xc0000005
Fault offset: 0x0041ba90
Faulting process id: 0x2598
Faulting application start time: 0x01cda3343028cf15
Faulting application path: C:\program files (x86)\ispy\ispy\ispy.exe
Faulting module path: C:\Program Files (x86)\iSpy\iSpy\avcodec-53.dll
Report Id: dbceda74-0f28-11e2-98c8-001ec957f8de

I am planning on eventually having iSpy recording 21 cameras on motion 
detection and displaying 12 cameras 24/7 across 2 monitors. Please help with 
this issue.

Original issue reported on code.google.com by velvetst...@gmail.com on 5 Oct 2012 at 8:31

[GoogleCodeExporter]

I stopped all the new cameras that I added today and now I am back to the 5 
that I had yesterday and everything is running fine. Is there a limitation on 
how many cameras can be configured?

Original comment by velvetst...@gmail.com on 5 Oct 2012 at 10:43

[GoogleCodeExporter]

Hello no there isn't - only however many your computer can handle. It could be 
a specific camera emitting broken frames that is throwing this error - try 
cyling through the cameras to find out which one it is.

Original comment by ad...@developerinabox.com on 8 Oct 2012 at 12:39

[GoogleCodeExporter]

I didn't think that resources would be an issue before posting this but after 
your reply I checked them. With 5 cameras running the server is using 53% of 
the 2x Quad-Core 2.33GHz CPU's and 3.5GB of 8GB of memory. I added 2 [7 total] 
more cameras and the server was at a solid 80% CPU's and the memory stayed the 
same. Adding 1 more camera [8 total] iSpy immediately crashes. This leaves the 
CPU running at less than 10%. Restarting iSpy spikes the CPU up to 84% 
immediately [7 cameras total].

Any suggestions on settings such as resolution, FPS, etc or a different 
hardware setup to record and display 21 cameras? Really I need all 21 recording 
and maybe 12 displayed.

Original comment by velvetst...@gmail.com on 8 Oct 2012 at 3:03

[GoogleCodeExporter]

umm no - recording 21 cameras will take some serious hardware. Best bet is to 
use multiple PCs for that. It's not just writing still frames, it's transcoding 
still frames into an mp4 file. I'd also guess that your hard drive will be 
struggling with writing 21 video feeds to disk at the same time (probably 
causing buffer over-runs)

Original comment by ad...@developerinabox.com on 25 Oct 2012 at 6:24

• Changed state: WontFix