Quietly we read <WAwuXSWYiFnEFwBw@user-unknown.mx2.org.uk>, unable to contain our credulity we realized that Pedt <"\"@ @\""@user-unknown.mx2.org.uk> said this:

In message <U8v1d+BjoZmEFxLX@blueyonder.co.uk>, at 05:11:11 on Thu, 22 Jun 2006, Bill Jillians <"\"Bill Jillians\""@blueyonder.SPAM_NO_THANKS.co.SPAM_OFF.uk> wibbled

Quietly we read <129g470jgcp3j38@corp.supernews.com>, unable to contain our credulity we realized that Klaatu <mutster8_nospam_@netscape.net> said this:

Bill Jillians wrote:

I downloaded a WU about two weeks ago and it is just ticking by.  I have
no idea why is  using so little system resources.  I haven't changed any
of the settings and usually when a WU is running the CPU usage is 100%.
With this WU it is barely 10%.  I'm loath to run this machine now seeing
as I'm wasting so much power getting so little done.  The estimated time
is 80 hours.  Usually it is 20.

Does anyone know what is going on with this unit???

See this recent thread "Hanging workunit and odd credit claims problem
solved." http://setiathome.berkeley.edu/forum_thread.php?id=31554
Maybe it applies to you, but you haven't posted very much specific
information, the wu # or OS for instance, so hard to tell.

"...
Thanks to some clues from Josef Segur and Tetsuji Rai, I've located the
cause of the "overflow results that hang" problem. It appears that it
wasn't an application issue at all, but a problem with the splitter that
resulted in thresholds that were set too low in such a way that the triplet
finder attempted to do an infinite amount of work.

This is also the cause of some long running workunits asking for too little
credit.

The problem has been fixed and I've started the new splitters. Once these
results get cleared the problem should go away. I'm working on a script to
fix the problem..."

Sorry

Computer P3-600, 96Mb RAM, Windows 98SE
Unit 23mr99aa.20172.3218.223594.2.14_1
I think the most important point which isn't covered in your thread is how little resources this WU is using compared to the usual 100% commitment when set to "always run".

I had one of the problem WUs a bit ago. 2 days and counting when the longest previously was ~12hrs. It was using IIRC about 10% of CPU time when I noticed and aborted it. Have a look at the other results from others for the unit. I'd guess that you'll find, like I did, they've all got errors.

I've had 3 more problem units.  Every unit I got yesterday was a problem.  I don't know whether to give it a break or crunch for 2.5 times as long as they usually take.