When can you say there is a problem ?
So after how many minutes/hours you should stop and restart the client or even stop the job ?

Now running for 20 minutes and still 1%.

New Wus with _omega_ take much longer than the old ones, my P4 needs 1-1,5h to jump to 20%, its a little bit confused because the checkpoints here are 20,40,60,80,100. Finished some in 2:20h or up to 4h.

It is a bit confusing, I agree, because now I have one at 10% after just 7 minutes.
But having it running during your work and coming home to find it still at 1% is not funny.
We'll see.

---

When can you say there is a problem ?
So after how many minutes/hours you should stop and restart the client or even stop the job ?

Now running for 20 minutes and still 1%.

Indeed! I currently have one "stuck" @ 10%
I even allocated more resource share
gonna let it crunch on, "says" 17h to compleation

---

Indeed! I currently have one "stuck" @ 10%
I even allocated more resource share
gonna let it crunch on, "says" 17h to compleation

You are on a Mac - I've seen this same problem. First, make sure that you're set to "leave application in memory". Rather than increase resource share, it would be even better to "suspend" everything else and let Rosetta crunch on this one non-stop. I had one that took 31 hours to complete... the good news is that I got something like 120 credits for it when it finally _did_ finish.

---

I did suggest that a time "cap" be placed on the start up of a work unit, though it was pointed out that the use of a fixed amount of time is not viable...

It looks like there is a least some kind of cap present.
resultid=1372617 reports "Maximum CPU time exceeded" after 60,359.58 CPU time.

It hasn't been sent to another user, perhaps the project team can investigate this one?

I've had 6 WU's like that "Maximum CPU time exceeded" in the last 12 hours on 6 different Computers, I'm starting to get a severe case of the Jitters running any of these WU's.

They all seem to get the Error around the 6:34:00 CPU Time Mark for what ever reason even though I've had WU's run longer than that and Complete Successfully ...

Is anybody else getting these "Maximum CPU time exceeded" Error's, I've had 6 more of them since this morning ... ??? Thats probably around 75 hours on my Computers of wasted CPU Time in the last 24 hr's for me ... :/

If there is a set Time Limit before they Error out maybe it needs to be increased ... ???

Is anybody else getting these "Maximum CPU time exceeded" Error's

I note the original WU with that error (by relic) was running BOINC 4.45. What version of BOINC are you using, Poorboy? I'm running 5.2.6 on most of my machines and have never seen that error (or a WU that took 16-17 hours).

I have had only 1 error in the last week (with about 200 WU completed)

---

*** Join BOINC@Australia today ***

I'm running version 5.2.7 right now, it seems the Errors may have started about 4 or 5 days ago right about the time I installed it. I was running v5.2.6 myself before that and never noticed any errors. I may switch back again if they continue just to see if I get any with it.

Indeed! I currently have one "stuck" @ 10%
I even allocated more resource share
gonna let it crunch on, "says" 17h to compleation

You are on a Mac - I've seen this same problem. First, make sure that you're set to "leave application in memory". Rather than increase resource share, it would be even better to "suspend" everything else and let Rosetta crunch on this one non-stop. I had one that took 31 hours to complete... the good news is that I got something like 120 credits for it when it finally _did_ finish.

Thanks, I'll give it a try
Sir Tralfaz

---

Thanks, I'll give it a try

Um... it's already been another 24 hours - if it's had that much run time and is STILL on 10%, I'd abort it...

---