Messages

1

iCam Support / Re: iCamSource.exe has stopped working...

« on: November 05, 2010, 06:42:41 PM »

Not sure, but I suspect it's when I try to connect.  A typical scenario is that I receive notification of a motion event when I'm away from home, and then find that I can't connect.  When I get home I see the "has stopped working" dialog.  Of course, other items I get the notification and can connect fine, so it's pretty hit or miss.

2

iCam Support / Re: iCamSource.exe has stopped working...

« on: November 04, 2010, 07:33:27 PM »

Yes, the MJPEG radio button is selected.  CPU usage is about 6-8%.  Frame rate is 5 fps.  Resolution is VGA high quality.  Things were more stable under iCamSource 1.x.  I'll experiment by dropping the video quality and rate even further.

3

iCam Support / Re: iCamSource.exe has stopped working...

« on: November 04, 2010, 11:18:40 AM »

URL is http://192.168.2.10/cgi/mjpg/mjpeg.cgi.  The model is IP-3G ConnectCam 1000.

4

iCam Support / Re: iCamSource.exe has stopped working...

« on: November 03, 2010, 06:40:23 PM »

Version 2.1.5 with a single wi-fi Swann camera on Windows Vista.  Computer is not going into standby or sleep mode.  It was stopped again today.  

Here's some additional information I collected after windows gave the "iCamSource.exe has stopped working" dialog.  Its status reported as "running" seems a bit contradictory, but I imagine that just means the application had surrendered its memory, etc... yet.

Image Name      PID Session Name   Session#   Mem Usage    Status      CPU Time
iCamSource.exe   5772 Console                    1      66,472 K    Running        3:45:15 N/A

So it was using a reasonable amount of memory -- eliminating memory leak as a cause.

5

iCam Support / Re: iCamSource.exe has stopped working...

« on: November 02, 2010, 07:07:04 PM »

I'm having a recurring problem with iCamSource.exe halting after about a day of operation.  Here is info from the Windows event log:

Faulting application iCamSource.exe, version 0.0.0.0, time stamp 0x4cbc7028, faulting module MSVCR90.dll, version 9.0.30729.4148, time stamp 0x4a594c79, exception code 0xc0000417, fault offset 0x0006ccb5, process id 0x1280, application start time 0x01cb7980745b5f9c.

I've got a watchdog process to restart it, but this is getting annoying.

6

iCam Support / Re: Memory leak on Windows Vista -- Resolved

« on: September 23, 2010, 07:46:02 AM »

I think I found the source of the problem.  I realized last night that when the task manager showed iCamSource using 100's of MB of data and acting sluggish, the time stamps on the camera images were about 40 minutes behind the current time.  So it looks like iCamSource was having trouble keeping up with the frame rate of the camera, creating a growing backlog of images.  I changed the camera configuration to operate at 5 fps and it's been working fine ever since.

7

iCam Support / Re: After reboot, iCamsource won't run

« on: September 22, 2010, 07:58:08 AM »

I find that the script to clean the registry works at first, but the problem recurs later after some number of stops and restarts.  I've decided to regress back to 1.4.2 for now.

8

iCam Support / Memory leak on Windows Vista

« on: September 21, 2010, 08:26:51 AM »

Since the beginning, I've been experiencing a memory leak on a Windows Vista machine using version 1.4.x and a swann wi-fi camera on a local wi-fi network.  I find the problem is still there with version  2.1.1.  After letting it run last night, the memory usage was up to almost 1 GB and the program was unresponsive.  I've confirmed that there are no outstanding updates on my Windows Vista installation.

I've set up  a watchdog script to stop and restart iCamSource when then memory usage exceeds 400 MB, but would certainly like to avoid that.

Regards.