CPU type GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz
Number of CPUs 2
Operating System Microsoft Windows XP Professional Edition, Service Pack 2, (05.01.2600.00)
Memory 503.48 MB
Cache 976.56 KB
Swap space 1229.98 MB
Total disk space 74.52 GB
Free Disk Space 55.79 GB
Measured floating point speed 1334.88 million ops/sec
Measured integer speed 1659.82 million ops/sec
Average upload rate 2.98 KB/sec
Average download rate 194.4 KB/sec
Average turnaround time 0.87 days
Results 17
Number of times client has contacted server 27
Last time contacted server 13 Mar 2005 4:01:58 UTC
% of time client is on 99.7542 %
% of time host is connected 96.7303 %
% of time user is active 100 %
Location Home
It returned another error since I turned off the screensaver. Is it just the screensaver I need to turn off or can I not use the Graphics at all?
Probably all graphics. After an early look at the graphics I haven't been showing them since I started trying to get to the bottom of this problem. My screen saver only ever shows me the BOINC logo and the percentage of work done on the current project. I think this due to the fact that I have Windows lock my account before it kicks in. I don't know if 4.24 of BOINC says the same but on 4.19 of BOINC the screen saver said something that gave me the impression that "basic" graphics were only being shown for this reason and that it was something that might be enhanced in a future release. In any case, basic graphics is all I get in the 4.24 screen saver - no project specific graphics unless I request them.
Having turned the screen saver off again earlier today, guess what? I've just processed a successful unit for the first time since I last switched it on. The actual crash may occur during project switching as per my last log but an enabled screen saver seems to be a necessary agent in the mix somewhere, to crash Einstein. Frank's observation is consistent with this. Maybe SETI is well behaved with BOINC (after all, they wrote it) but CPDN and Predictor are abusing shared memory as Walt suggests and Einstein is suffering during shut down? That could account for why Vladimir is OK (only SETI and Einstein) but the rest of us have problems.
Wow, I went away for 48 hours and the scat seems to have hit the fan. At least lots of people are using it, but now word is getting around they better fix it or else this project could be dead before its really begun.
Yeah, I turned of graphics and I've only had one failed unit since then, I hope they get around to fixing it at one point though.
Did your client ever actually crash, because my screen saver worked fine, But when I checked at the end there were errors. I never really looked during computation. But the one time I did, there was.
My BOINC client has never crashed as such, only the Einstein program whihc is then handled gracefully by BOINC. I might not have noticed anythnig was wrong except when I checked the computation errors in the results. The problem definitely seems to coincide with having the screen saver enabled in BOINC 4.24. Logging shows that the Einstein crash occurs when switching processing between projects, but an activated BOINC screen saver seems to be the triggering factor.
Screen saver disabled = switching between projects fine.
Screen saver enabled = all my Einstein work units returned with errors which occur as Einstein is paging out and another project is paging in to memory.
I suppose this might also work correctly for poeple who have "leave in memory" set to true, 'cos then the system is obviously handling memory management differently and memory management looks like the problem.
> > I've currently processed eleven complete work units and of these all but
> the
> > first one are shown as "client errors" with no credit awarded. I'm using
> BOINC
> > 4.24 and I'm splitting time with all the other open BOINC projects. I'm
> > beginning to wonder if there's some problem with my set up for
> Einstein@home.
> > Am I just very unlucky or is there a deeper problem? What is likely to
> cause
> > the "client errrors" and is there anything I cn do about it?
>
> If you look at the results on the web, you'll see that stderr_out is showing
> repeated access violations at a particular address in memory. This is not an
> address within the Einstein@Home application. So it may be related to a
> graphics driver misbehaving, bad memory in your system, or some other similar
> system problem. Any idea what was different for the successful workunit?
>
> Cheers,
> Bruce
>
Hello,
I do have the same problem.
I had seti running with boinc version 4.19
I joined einstein, and everything worked fine.
I than installed 4.25, and since then, I have systematic client errors with this memory problem.
Note that seti seems to work fine.
I noted also that sometimes the screensaver does not get launched. I do not know if it is related.
By the way the screensaver which is running is the einstein one. I do not know how to switch to the seti one, but it could be a good try.
I don't think it is a specific application screen saver, but rather BOINC launching any screen saver. The only screen saver I can get is a default BIONC one probably because of the way my windows security is set up. This only shows which project it is running and a percentage completed in a simple text box which is periodically displayed at different locations on the screen. But it appears to be sufficient to break Einstein without ever showing the Einstein graphics. I don't know how you'd switch to SETI graphics and not show Einstein ones (or even if you can) although it sounds like an interesting experiment. But I think your best bet, if your system behaves like mine, is to switch off the screen saver altogether (i.e. set it to blank) then I think you might find your problem goes away...
For what it's worth, my system managed to complete 2 wu's without client errors after I stopped displaying Einstein graphics using BOINC 4.25's "show graphics" command on any Einstein WU's. Prior to this my system experienced 5 consecutive client errors on Einstein WU's after installing BOINC V 4.25 and then displaying and closing the Einstein graphics display window for each WU.
My system runs using BOINC single user mode, SETI 1/3 and Einstein 2/3, leaving both applications in memory when switching projects, without using the Einstein or SETI screensaver functions.
The client errors occurred only after closing the Einstein graphics display window and only with BOINC V 4.25. Einstein application V 4.79 didn't exhibit this problem with BOINC V 4.19. SETI graphics display window closing causes no client error in either BOINC version.
I suspect if you stop using the screensaver graphics (a pity as it's impressive)and not use BOINC V 4.25 manager's show graphics commands to display Einsetin graphics, you may eliminate the client errors experienced under BOINC V 4.25.
After a couple of experiments, I confirm, it is the screensaver or show graphics which is the cause of the crashes. The option of leaving or not the application in memory does not change anything.
I guess we need to wait for the next release of Boinc or Einstein to have both a nice screensaver and to do some usefull work.
Is there a way to report bugs, or should we just hope.
> I guess we need to wait for the next release of Boinc or Einstein to have both
> a nice screensaver and to do some usefull work.
The Apps we put on the server work without these problems for 99,5% of the people including the developers who test them beforehand. I've set up quite some systems myself in the last two weeks without observing problems with the screensaver (apart from some experimental code I tested). If there is a problem, it is more likely to be bound to your specific system configuration than to the E@H or BOINC code.
> Is there a way to report bugs, or should we just hope.
We are reading the forums (though might be too busy sometimes for an immediate response).
In this case, however, I don't think that a new App would help. You seem to have a problem with your graphics hard- or software.
CPU type GenuineIntel
)
CPU type GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz
Number of CPUs 2
Operating System Microsoft Windows XP Professional Edition, Service Pack 2, (05.01.2600.00)
Memory 503.48 MB
Cache 976.56 KB
Swap space 1229.98 MB
Total disk space 74.52 GB
Free Disk Space 55.79 GB
Measured floating point speed 1334.88 million ops/sec
Measured integer speed 1659.82 million ops/sec
Average upload rate 2.98 KB/sec
Average download rate 194.4 KB/sec
Average turnaround time 0.87 days
Results 17
Number of times client has contacted server 27
Last time contacted server 13 Mar 2005 4:01:58 UTC
% of time client is on 99.7542 %
% of time host is connected 96.7303 %
% of time user is active 100 %
Location Home
It returned another error since I turned off the screensaver. Is it just the screensaver I need to turn off or can I not use the Graphics at all?
Probably all graphics. After
)
Probably all graphics. After an early look at the graphics I haven't been showing them since I started trying to get to the bottom of this problem. My screen saver only ever shows me the BOINC logo and the percentage of work done on the current project. I think this due to the fact that I have Windows lock my account before it kicks in. I don't know if 4.24 of BOINC says the same but on 4.19 of BOINC the screen saver said something that gave me the impression that "basic" graphics were only being shown for this reason and that it was something that might be enhanced in a future release. In any case, basic graphics is all I get in the 4.24 screen saver - no project specific graphics unless I request them.
Having turned the screen saver off again earlier today, guess what? I've just processed a successful unit for the first time since I last switched it on. The actual crash may occur during project switching as per my last log but an enabled screen saver seems to be a necessary agent in the mix somewhere, to crash Einstein. Frank's observation is consistent with this. Maybe SETI is well behaved with BOINC (after all, they wrote it) but CPDN and Predictor are abusing shared memory as Walt suggests and Einstein is suffering during shut down? That could account for why Vladimir is OK (only SETI and Einstein) but the rest of us have problems.
Wow, I went away for 48 hours
)
Wow, I went away for 48 hours and the scat seems to have hit the fan. At least lots of people are using it, but now word is getting around they better fix it or else this project could be dead before its really begun.
Yeah, I turned of graphics and I've only had one failed unit since then, I hope they get around to fixing it at one point though.
Did your client ever actually crash, because my screen saver worked fine, But when I checked at the end there were errors. I never really looked during computation. But the one time I did, there was.
My BOINC client has never
)
My BOINC client has never crashed as such, only the Einstein program whihc is then handled gracefully by BOINC. I might not have noticed anythnig was wrong except when I checked the computation errors in the results. The problem definitely seems to coincide with having the screen saver enabled in BOINC 4.24. Logging shows that the Einstein crash occurs when switching processing between projects, but an activated BOINC screen saver seems to be the triggering factor.
Screen saver disabled = switching between projects fine.
Screen saver enabled = all my Einstein work units returned with errors which occur as Einstein is paging out and another project is paging in to memory.
I suppose this might also work correctly for poeple who have "leave in memory" set to true, 'cos then the system is obviously handling memory management differently and memory management looks like the problem.
> > I've currently processed
)
> > I've currently processed eleven complete work units and of these all but
> the
> > first one are shown as "client errors" with no credit awarded. I'm using
> BOINC
> > 4.24 and I'm splitting time with all the other open BOINC projects. I'm
> > beginning to wonder if there's some problem with my set up for
> Einstein@home.
> > Am I just very unlucky or is there a deeper problem? What is likely to
> cause
> > the "client errrors" and is there anything I cn do about it?
>
> If you look at the results on the web, you'll see that stderr_out is showing
> repeated access violations at a particular address in memory. This is not an
> address within the Einstein@Home application. So it may be related to a
> graphics driver misbehaving, bad memory in your system, or some other similar
> system problem. Any idea what was different for the successful workunit?
>
> Cheers,
> Bruce
>
Hello,
I do have the same problem.
I had seti running with boinc version 4.19
I joined einstein, and everything worked fine.
I than installed 4.25, and since then, I have systematic client errors with this memory problem.
Note that seti seems to work fine.
I noted also that sometimes the screensaver does not get launched. I do not know if it is related.
By the way the screensaver which is running is the einstein one. I do not know how to switch to the seti one, but it could be a good try.
Any hints ?
Cheers,
Michel.
Michel.
I don't think it is a
)
I don't think it is a specific application screen saver, but rather BOINC launching any screen saver. The only screen saver I can get is a default BIONC one probably because of the way my windows security is set up. This only shows which project it is running and a percentage completed in a simple text box which is periodically displayed at different locations on the screen. But it appears to be sufficient to break Einstein without ever showing the Einstein graphics. I don't know how you'd switch to SETI graphics and not show Einstein ones (or even if you can) although it sounds like an interesting experiment. But I think your best bet, if your system behaves like mine, is to switch off the screen saver altogether (i.e. set it to blank) then I think you might find your problem goes away...
For what it's worth, my
)
For what it's worth, my system managed to complete 2 wu's without client errors after I stopped displaying Einstein graphics using BOINC 4.25's "show graphics" command on any Einstein WU's. Prior to this my system experienced 5 consecutive client errors on Einstein WU's after installing BOINC V 4.25 and then displaying and closing the Einstein graphics display window for each WU.
My system runs using BOINC single user mode, SETI 1/3 and Einstein 2/3, leaving both applications in memory when switching projects, without using the Einstein or SETI screensaver functions.
The client errors occurred only after closing the Einstein graphics display window and only with BOINC V 4.25. Einstein application V 4.79 didn't exhibit this problem with BOINC V 4.19. SETI graphics display window closing causes no client error in either BOINC version.
I suspect if you stop using the screensaver graphics (a pity as it's impressive)and not use BOINC V 4.25 manager's show graphics commands to display Einsetin graphics, you may eliminate the client errors experienced under BOINC V 4.25.
Hello, After a couple of
)
Hello,
After a couple of experiments, I confirm, it is the screensaver or show graphics which is the cause of the crashes. The option of leaving or not the application in memory does not change anything.
I guess we need to wait for the next release of Boinc or Einstein to have both a nice screensaver and to do some usefull work.
Is there a way to report bugs, or should we just hope.
Cheers,
Michel.
I ran opened and ran
)
I ran opened and ran graphical mode too long (Just a couple of seconds) and I got an error.
I shouldn't have tempted fate :D
> I guess we need to wait for
)
> I guess we need to wait for the next release of Boinc or Einstein to have both
> a nice screensaver and to do some usefull work.
The Apps we put on the server work without these problems for 99,5% of the people including the developers who test them beforehand. I've set up quite some systems myself in the last two weeks without observing problems with the screensaver (apart from some experimental code I tested). If there is a problem, it is more likely to be bound to your specific system configuration than to the E@H or BOINC code.
> Is there a way to report bugs, or should we just hope.
We are reading the forums (though might be too busy sometimes for an immediate response).
In this case, however, I don't think that a new App would help. You seem to have a problem with your graphics hard- or software.
BM
BM