My computer is having an issue at the moment. I don't know if it has to do with work unit 1435 being long, but I get about 2 to sometimes 3 hours into a work unit then it switches to another. Works on that one for a while then switches again. The work unit it switches to run says "Running in High Priority". So I'm guessing having the long work units running along side the shorter deadline ones are messing with my system.

Does it reset the workunit progress when it switches?

i'm getting this on 1457 (the unit BOINC paused to give another one priority has been running for just short of 9 hours). not sure how THIS one will turn out, but in the past, it's only ever resumed to a unit error.

Which version of BOINC are you using?

I'm getting the same thing for the blender task on my dual core linux machine running 6.12.42. It's especially annoying because I have it set to use only one core and I only have enough ram for one task. It pretty much locks up my computer until I abort one of them. This is probably a boinc issue, though.

Is this a recently installed host? Sometimes it takes a while for the client to figure out how to handle work for all the projects it's assigned to. You might want to check your settings such as "Switch between tasks every..." and "Maintain enough work for an additional..." so your client isn't asking for any more work when it's already got a task, or switching between them.

---

Click here to see My Detailed BOINC Stats

Edit:
Sorry, posted before looking... ;-)

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Is this a recently installed host? Sometimes it takes a while for the client to figure out how to handle work for all the projects it's assigned to. You might want to check your settings such as "Switch between tasks every..." and "Maintain enough work for an additional..." so your client isn't asking for any more work when it's already got a task, or switching between them.

Been running boinc on mine for roughly 3 years (the one switching back and forth). Even after reducing the "Maintain enough..." setting down to a day, it was still doing it. I think all my machines are set to 60 minutes for the switch option.

I recommend setting "Switch every.." as high as possible to avoid switching away from started BURP units at any time. One of the current client's weaknesses is that it doesn't like being paused/switched.