When I suspend the individual tasks, or even the whole project, the tasks continue to run. BOINC shows them as suspended, but you can see they are still running in the task manager. This is for both linux and windows.

I can confirm this on v2.29 win, the BOINC wrapper is working correctly and send all start/stop/resume to BOINC client but the app itself is running further in background.

This issue has now been fixed server-side for both Windows and Linux. New tasks correctly suspend the solver process when an individual task or the entire BOINC project is suspended, and resume it afterward.
Tasks downloaded before the fix still use the previous configuration, so the old behavior may remain until those tasks have finished. No application update or user action is required. Thank you for reporting and confirming the issue.

Thanks!

I experienced some strange behavior. I suspended BOINC, and when I resumed it, every task in progress jumped to 100% and finished immediately.

On which app version was that? I had this on win v2.35 but was fixed in v.2.37 (suspend was not working)

In reply to rebirther's message of 12 Oct 2026:

On which app version was that? I had this on win v2.35 but was fixed in v.2.37 (suspend was not working)

Eternity II CPU solver (pilot) 2.37 under Linux

Edit: Maybe its something with the internal timer? I suspended Boinc for about 3 hours. If I suspend and restart shortly after everything seems ok. I will test more :)

Thanks Stiwi, and thanks rebirther for narrowing it down. You found a real bug: each task had a time limit that counted real elapsed time instead of computing time. When BOINC kept a suspended task in memory, that clock kept running, so after a suspension longer than about 2 hours the task hit its limit as soon as it resumed and finished early.

It's fixed in version 2.40, released today for Windows and Linux. The limit now counts only actual computing time, so suspending BOINC, even for a long time, no longer ends your tasks. We've also made tasks shorter, about one hour of computing each. Tasks you had already downloaded in 2.37 can still show the old behaviour until they're finished; all new tasks use 2.40.

Thanks for reporting it so precisely!

this was waste

You're right that it was annoying, sorry about that. The good news is that the computing itself wasn't thrown away: when a task hit that limit, the tickets it had already finished were reported and saved, and the unfinished ones went back into the queue for other tasks. What you lost was the rest of the task, not the work already done. Since 2.40 the limit only counts actual computing time, so suspending BOINC, even for a long time, no longer ends your tasks.