iSpy has stopped working
Opened this issue · 3 comments
GoogleCodeExporter commented
I get multiple crashes throughout the day, with this message from Windows 7:
iSpy has stopped working
A problem caused the program to stop working correctly. Windows will close the
program and notify you if a solution is available.
Button to Close Program
On pressing the Close Program button, iSpy restarts and continues as normal.
The iSpy log file for the time of a particular crash, about 12:15pm, says:
Log Start (v4.7.1.0): Thursday, 6 December 2012
Message 11:53:36 AM Checking Plugins...
Message 11:53:36 AM Running External Command: open
C:\Users\Ian\AppData\Roaming\iSpy\XML\objects.xml
Other earlier log files have similar entries.
This crash occurs several times during the day and night. Usually, iSpy will
restart itself but the video files for the 15 minute period around those times
contain only 1kB. Sometimes, iSpy will run fine for 3 or 4 hours and then crash
once or twice in an hour, even during the middle of the night when nothing else
is running.
This has been happening for the 2 weeks that I have been running iSpy. I can
find no pattern to the crashes. I have rebooted, re-installed, checked for the
latest software, ensured Windows 7 is up to date, and so on.
What can I do to fix this problem? I have searched through Forum posts (user
IanT) but nothing similar seems to have been reported.
I run Windows 7 64-bit service pack 1 on an Intel Core i7 CPU 920 @ 2.67GHZ
with 6GB memory. I have assigned 150GB local RAID disk space for video files
but only 11GB has been used so far.
I did have my 2 networked generic IP cameras running at 1028 x 720. I have
downgraded them to 640 x 480 but the problem remains.
Thanks for your help.
Ian
Original issue reported on code.google.com by secretar...@gmail.com on 6 Dec 2012 at 4:47
GoogleCodeExporter commented
Further to my earlier report, from time to time I get another message from
Windows when iSpy crashes, saying:
Micrsoft Visual C++ Runtime Library
This aplication has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Does this shed light your investigations?
Ian
Original comment by secretar...@gmail.com on 8 Dec 2012 at 9:12
GoogleCodeExporter commented
GoogleCodeExporter commented
I think those other instances are the windows error reporting windows
check the event logs in windows and if relevant change your VLC sources to use
FFMPEG instead.
Original comment by ad...@developerinabox.com on 12 Dec 2012 at 2:57