Lack of virtual memory causing client errors?
25 Oct 2007 20:18:47 UTC
Topic 193269
(moderation:
I've got 2 client errors lately while I've never got one before that.
However, there's a coincidence: Now and then one of my selfmade programs malfunctioned and ate up all available virtual memory (on Windows XP), thus preventing other processes from allocating new memory (at least until I noticed that and had the chance to kill the malfunctioning process).
Can this be the reason for those client errors?
Lack of virtual memory causing client errors?
)
Thanks for reporting those errors.
This is kind of interesting, one of the failed results definitely looks like an out-of-memory problem The other error is somewhat more mysterious but it helps to see that those kind of errors might be provoked by memory resource problems.
CU
Bikeman
RE: This is kind of
)
Maybe
while (malloc() == 0) sleep(1000)helps?Could a lack of memory have prevented BOINC (or whoever) from reporting the error?
RE: Maybe while (malloc()
)
Hmm...don't like this too much. In the rather critical event of a memory shortage, software that is meant to run only on idle cycles should just terminate, gracefully releasing its memory to more critical processes so the user has a chance to continue work on that PC or at least restart the PC in a controlled fashion.
CU
Bikeman
RE: RE: The other error
)
The problem here is that BOINC 5.8 uses memory preferences, either set through the website or through BOINC Manager (Advanced View, Advanced, Preferences on 5.10), and when it finds it is out of memory any application will go wait with a message "Waiting for memory".
Now, that's normal memory (RAM) we're speaking of.
The amount of virtual memory you want BOINC to use is also set through the preferences, plus of course set in the operating system itself. You won't be able to tell BOINC to use more VM than you have set your page file or swap space for (good thing those percentages).
I think that the error with the comment of the ownership of the semaphore having ended has to do with shared memory, which is a block of memory used by multiple CPUs. The problem here is that your CPU looks like it's a single one, correct? You don't have more than one CPU in your system and it's not multi-cored or whatever?
The other error you have is because a dynamic linked library failed to load. The last time I checked, Bernd was still wonder what DLL that might be. It happens mostly on Vista, but XP can do it as well.
If it stays at those two errors, you have not much to worry about. If it happens again, first try a newer BOINC version. It may have been fixed in a newer version and we're up to 5.10.20 now.
RE: I think that the error
)
Yes, that's correct. It's a single core Athlon XP CPU.