BOINC 5.8.16 running as a service on WinXP Pro.

I am attached to Rosetta, Malaria, and Seti on a Pentium D. I have set my "switch every interval" to 300 minutes to allow work units to complete before switching.

The machine has been on overnight. I just noticed that there is a completed Seti and Malaria WU to upload. There is a Rosetta WU running (1:30 and 50%) and a Malaria WU at (1:00 and 75%). There are no report deadlines for the next couple of days. All short term debt values are between +1000 and -1000. Nothing odd there. But there is another Rosetta WU sitting at 2:15 and 75% "Waiting to run".

There are WUs from all projects waiting to start. I am a bit baffled why the one Rosetta WU might have gotten stopped, and even more baffled why it would have started a new Rosetta with one partially completed. The one waiting has a deadline closer than the one running.

Of course, in a few hours I'm sure they will all be completed, uploaded, and gone from sight. but it does seem odd.

---

Shortly after I posted here, a couple of WU's finished and it started others. So I decided it probably was a Rosetta problem and posted there. Now looking at the log, the only mention of that WU was the two lines when it started. Nothing about stopping or pausing it. Oh well, the CPU ate it. Curious, but no big deal.

the few times I've seen this behaviour is actually with a message 'waiting for memory' when a model got too big for the ram allocated to BOINC. The defaults for memory allocation is I think still 50% when in use and 90% when idle (from the 5.8.x versions). Have you checked at the Rosetta forum?

---

It might also have been that it was running 2 rosetta's at once and then later decided to run only one of them. Especially at startup one project will most likely get both cores for a while before it changes one of them.

---

BOINC WIKI

BOINCing since 2002/12/8