So, what does the core client need desktop heap space for anyway?
Every (non-console) Windows App needs a fragment of "Desktop Heap", or the KERNEL32.DLL and USER32.DLL will fail to load. In particular this applies to the BOINC Apps started by the client. If the Desktop heap is full, the App can't be started, which results in a Client Error that indicates a DLL load problem.
BM
This probably needs to go over to a Windows thread, but I'd be curious to know if it happens with older BOINC versions, say 5.4.11 or 5.8.16.
This probably needs to go over to a Windows thread, but I'd be curious to know if it happens with older BOINC versions, say 5.4.11 or 5.8.16.
It has nothing to do with the BOINC Core Client. I found 1170 of these errors from 5.4.x Clients in the DB, and 1841 from 5.8.x Clients. Believe me?
I wouldn't have doubted you. I guess I was thinking of GUI/Screensaver/Tray changes that happened lately that could've pushed the envelope...
Frankly, I think all the startup stuff that every software installation wants to add has gotten absurd. I am going over to a classmate's house to work on school together (instructor assigned us as partners) and her computer has like 15 tray icons. Even mine has 6 tray icons, including BOINC. All that consumes resources. It seems like EVERYONE has to shove their stuff up "front and center", as it were, to either "get attention" or "make it easy to launch". MSCONFIG for mine shows 25 items checked to run at startup. 25! Everything from AOL to my Logitech mouse to Quicktime to a bunch of Creative Labs stuff for my X-Fi... So, perhaps even a reboot won't "fix" the problem, if you have someone that has installed a whole bunch of stuff that launches at startup...
Exit code -185 ("can't start App") on Mac OS, probability increases with number of cores, happens frequently on 8 core Macs.
This is caused by a rather restrictive default for shared memory segments. See this messaeg for a MacOS configuration fix.
P.S.: We will consolidate this thread into a single list containing error codes and explanations for them a bit later, it's now getting a bit hard to find things here, sorry.
First, all the tasks you mentioned and that have been reported by your host so far were run with the standard App version 4.02.
I'm not completely sure that this covers all cases, but every time I have seen this error ("Input domain error") occurring myself was a machine with some (possibly transient) hardware problems.
Is the machine overclocked? Are you monitoring the CPU temperature? Is the machine standing somewhere where it gets hot (or so dusty that the CPU fan may suffer) occasionally?
First, all the tasks you mentioned and that have been reported by your host so far were run with the standard App version 4.02.
Hmm, I was quite sure to follow the instruction for the Version 4.16....
Quote:
I'm not completely sure that this covers all cases, but every time I have seen this error ("Input domain error") occurring myself was a machine with some (possibly transient) hardware problems.
Is the machine overclocked? Are you monitoring the CPU temperature? Is the machine standing somewhere where it gets hot (or so dusty that the CPU fan may suffer) occasionally?
I'm quite sure to have no HW problems, since I can calculate Seti and Climate WU's without errors.
My CPU is not overclocked - quite the oppusite, I clock down from 3200 to 2400, to get less noisy ;-)
Are there other possible errors, or should I try again with the 4.16
Thanks for the report. It
)
Thanks for the report.
It actually means that no signal handler (even in the 4.14 App) is catching this, which is a bad sign.
This isn't even a 64Bit machine right?
BM
BM
No, it is not a 64bit
)
No, it is not a 64bit machine.
It's an old AMD Duron 1600 ("Applebred") that I use as a small e-mail server.
RE: RE: So, what does the
)
This probably needs to go over to a Windows thread, but I'd be curious to know if it happens with older BOINC versions, say 5.4.11 or 5.8.16.
RE: This probably needs to
)
It has nothing to do with the BOINC Core Client. I found 1170 of these errors from 5.4.x Clients in the DB, and 1841 from 5.8.x Clients. Believe me?
BM
BM
What got moved in here was a
)
What got moved in here was a discussion that started over in the MacOS Beta App thread, but didn't really belong there.
BM
BM
RE: RE: This probably
)
I wouldn't have doubted you. I guess I was thinking of GUI/Screensaver/Tray changes that happened lately that could've pushed the envelope...
Frankly, I think all the startup stuff that every software installation wants to add has gotten absurd. I am going over to a classmate's house to work on school together (instructor assigned us as partners) and her computer has like 15 tray icons. Even mine has 6 tray icons, including BOINC. All that consumes resources. It seems like EVERYONE has to shove their stuff up "front and center", as it were, to either "get attention" or "make it easy to launch". MSCONFIG for mine shows 25 items checked to run at startup. 25! Everything from AOL to my Logitech mouse to Quicktime to a bunch of Creative Labs stuff for my X-Fi... So, perhaps even a reboot won't "fix" the problem, if you have someone that has installed a whole bunch of stuff that launches at startup...
Brian
Exit code -185 ("can't start
)
Exit code -185 ("can't start App") on Mac OS, probability increases with number of cores, happens frequently on 8 core Macs.
This is caused by a rather restrictive default for shared memory segments. See this messaeg for a MacOS configuration fix.
P.S.: We will consolidate this thread into a single list containing error codes and explanations for them a bit later, it's now getting a bit hard to find things here, sorry.
CU
Bikeman
Exit code 99: Hello, I
)
Exit code 99:
Hello,
I got 99 errors on my Linux Client.
It ist SuSe Linux 10.3, Boinc 5.10.28, and Einstein 4.16.
ResultID: http://einsteinathome.org/task/88670318
process exited with code 99 (0x63, -157)
Final Errors:
LocalXALComputeFaFb() failed
Error[2] 5: function LocalComputeFStat, file /home/bema/einsteinathome/HierarchicalSearch/EaH_build_release_einstein_S5R3_4.02/extra_sources/lalapps-CVS/src/pulsar/hough/src2/LocalComputeFstat.c, line 353, $Id: LocalComputeFstat.c,v 1.58 2007/09/17 14:00:37 bema Exp $
ABORT: XLAL function call failed
Error[1] -1: function LocalComputeFStatFreqBand, file /home/bema/einsteinathome/HierarchicalSearch/EaH_build_release_einstein_S5R3_4.02/extra_sources/lalapps-CVS/src/pulsar/hough/src2/LocalComputeFstat.c, line 218, $Id: LocalComputeFstat.c,v 1.58 2007/09/17 14:00:37 bema Exp $
Function call "LocalComputeFStat ( status->statusPtr, &Fstat, &thisPoint, multiSFTs, multiWeights, multiDetStates, params, &cfBuffer )" failed: Recursive error
Also:
http://einsteinathome.org/task/88667767
http://einsteinathome.org/task/88502891
Hope it helps,
Regards, Barney
First, all the tasks you
)
First, all the tasks you mentioned and that have been reported by your host so far were run with the standard App version 4.02.
I'm not completely sure that this covers all cases, but every time I have seen this error ("Input domain error") occurring myself was a machine with some (possibly transient) hardware problems.
Is the machine overclocked? Are you monitoring the CPU temperature? Is the machine standing somewhere where it gets hot (or so dusty that the CPU fan may suffer) occasionally?
BM
BM
RE: First, all the tasks
)
Hmm, I was quite sure to follow the instruction for the Version 4.16....
I'm quite sure to have no HW problems, since I can calculate Seti and Climate WU's without errors.
My CPU is not overclocked - quite the oppusite, I clock down from 3200 to 2400, to get less noisy ;-)
Are there other possible errors, or should I try again with the 4.16
Regards, Barney