When starting Zoom in Spider mode I obtain an error "Microsoft Visual C++ Runtime Error" - Runtime Error! without any other logs - Zoom or system log. In Offlline mode there are no errors. I have the latest version installed (windows XP prof / 4GB ram). I've installed the older version (1017) and the symptoms are the same.
Announcement
Collapse
No announcement yet.
Microsoft Visual C++ Runtime Error
Collapse
X
-
Can you E-Mail us your configuration file (xxxxxxx.zcfg) so that we can investigate the problem.
I assume the problem happens after you click on the "start indexing" button? If yes, then can you save the log file. (On the "index log" configuration window, check "debug mode" and specify a file name for the log). Then send us the log as well.
-
Got your trace files. But you didn't include all the details we asked for.
What hardware are you running this on?
Also which operating system?
Are you using the 32bit release of Zoom or the 64bit release?
You have set high limits in Zoom. RAM requirements are in excess of 2.5GB. Which is OK if you have good new 64bit hardware. But on old hardware, this isn't going to work.
Zoom still shouldn't crash however. But it should present an error message saying not enough RAM is available.
To reduce RAM usage reduce the max limits in the limits configuration window and / or reduce the number of indexing threads.
Comment
-
You should have received our further e-mails regarding this by now. But let us know if not (or check your spam filters).
To summarize for other people following this thread:- ecoca has set his Limits in Zoom very high, requiring more than 2.5GB of RAM.
- ecoca is using a 32-bit OS. Windows XP 32bit only allows each application to use up to 2GB of RAM. (this is despite that fact that you might have 4GB or more physically installed). Windows 64bit applications get 8 terabytes each.
- It is unusual for Zoom to crash like this even if you have asked it to use more RAM than it is available in Windows (we have tested this and could not reproduce it). It should normally gracefully abort the indexing and report that you do not have enough memory. There might be another problem here with your system specifically. Have you run Windows Update and installed all latest XP patches?
Comment
Comment