I had a WU stuck at 83.66% for 5 hours (2.8GHz P4). It suddenly jumped to 91.66, and then back to 83.66% per 5 or 6 times. I had to kill it.

Are you running more then one project on that computer, so that it is switching projects. If so, under general preferences try increasing the "time" between project switches to 120 minutes instead of the default 60. From 83.33% on, the calculations are more complex and take longer. Another option is to "leave in memory". I had this same problem, and increasing the time between switches solved it.

Also got a bad WU. After 2h and 1% I have aborted this.
WU 68187

I had a WU stuck at 83.66% for 5 hours (2.8GHz P4). It suddenly jumped to 91.66, and then back to 83.66% per 5 or 6 times. I had to kill it.

Are you running more then one project on that computer, so that it is switching projects. If so, under general preferences try increasing the "time" between project switches to 120 minutes instead of the default 60. From 83.33% on, the calculations are more complex and take longer. Another option is to "leave in memory". I had this same problem, and increasing the time between switches solved it.

I'll try this one out. Thanks

It happened to me with this last WU. 2 hours spent on 1%.
I had to abort the WU and resume, after that a computation error showed up.
And no, I don't release Rosetta from memory. Maybe I shall try to attribute rosetta to one logical CPU only to avoid what Shaktai is supposing here above me.
I think the devs must look seriously into this, because is affecting the whole BOINC efficiency very much.

I'm looking into it. Can everyone on this thread (no one else as I don't want too many emails) who is having the problem send me the stdout.txt files in slot0 and slot1 (if you are running dual cpu) in the BOINC installation? dekim at u.washington.edu.

Thanks,

David K

I've been watching my Windows PC's closer and the only machines that seem to get stuck at 1% are the dual core boxes, both the AMD and the Intel. My P4 3.4 ghz with HT hasn't had the problem yet that I've caught it, and none of the single CPU boxes have had it recently. The dual core boxes are experiencing it almost daily now, where one of the two units will get stuck at 1%. Each time, a simple restart of BOINC fixes it.

I've been watching my Windows PC's closer and the only machines that seem to get stuck at 1% are the dual core boxes, both the AMD and the Intel. My P4 3.4 ghz with HT hasn't had the problem yet that I've caught it, and none of the single CPU boxes have had it recently. The dual core boxes are experiencing it almost daily now, where one of the two units will get stuck at 1%. Each time, a simple restart of BOINC fixes it.

No, i've just got one HT machine, and it get stuck this morning at 83.33%

I've been watching my Windows PC's closer and the only machines that seem to get stuck at 1% are the dual core boxes, both the AMD and the Intel. My P4 3.4 ghz with HT hasn't had the problem yet that I've caught it, and none of the single CPU boxes have had it recently. The dual core boxes are experiencing it almost daily now, where one of the two units will get stuck at 1%. Each time, a simple restart of BOINC fixes it.

No, i've just got one HT machine, and it get stuck this morning at 83.33%

There are two different problems. One where it gets stuck at 1%, and the one where it gets stuck at 83.33%. For many folks the solution to the 83.33% issue was to "leave application in memory" and if running more then one project, to extend the time between "switches" from the default of 60 minutes, to 90-180 minutes (depending on the speed of the machine). With the 83.33%, the calculations become much more complex and take longer. If you are switching between projects every 60 minutes, then it may not reach the next step (91.66%) before the switch and then will restart at the 83.33% when it switches back. David Kim is looking at both of these issues for fixes.

There are two different problems. One where it gets stuck at 1%, and the one where it gets stuck at 83.33%. For many folks the solution to the 83.33% issue was to "leave application in memory" and if running more then one project, to extend the time between "switches" from the default of 60 minutes, to 90-180 minutes (depending on the speed of the machine). With the 83.33%, the calculations become much more complex and take longer. If you are switching between projects every 60 minutes, then it may not reach the next step (91.66%) before the switch and then will restart at the 83.33% when it switches back. David Kim is looking at both of these issues for fixes.

[b]"I'm trying to maintain a shred of dignity in this world." - Me[/b]