I had to pause a few AP tasks, because it was getting too hot.
However, without having downloaded new tasks, why is boinc starting new tasks, instead of finishing the ones, that have already been started and are waiting?

I had to pause a few AP tasks, because it was getting too hot.
However, without having downloaded new tasks, why is boinc starting new tasks, instead of finishing the ones, that have already been started and are waiting?

Boinc doesn't know why you pause tasks, so when you do, it moves onto another task. If you want to stop Boinc, in the Projects tab, suspend the project itself. Resume it when things have cooled down somewhat ;-)

P.

---

If you pause tasks, then BOINC will start new one's, when those are finished the waiting tasked should fire up.

---

What i mean is, that once the new task is finished, and the paused is in a waiting state, it starts another new one, not finishing the waiting one.
That is stupid, as the waiting task sits there hogging memory.

What i mean is, that once the new task is finished, and the paused is in a waiting state, it starts another new one, not finishing the waiting one.
That is stupid, as the waiting task sits there hogging memory.

You have attached, over the years, to roughly 40 projects, although not many are currently active. How many are running on the machine you're talking about? And, in particular, when you say a "new task" starts up, is it a task from SETI @ Home, or from another project?

If it's from another project, BOINC is simply honouring Resource Share - giving the other guys their time in the limelight.

I am just running seti, exclusively.