I have SiDock running on a couple of Raspberry Pis alongside TN-Grid and World Community Grid tasks. I have set BOINC to only use 2 of the Raspberry Pi cores to make sure that there aren't any memory problems.

I've noticed that when BOINC switches to other tasks and the SiDock task is "Waiting to run", then it is still running, as shown in Task Manager and by the checkpoint messages. See https://1drv.ms/u/s!ApiRP3wyITQrrhzwkP6XBu1Zujh9

Similarly, when the SiDock task is suspended, it still keeps running. See https://1drv.ms/u/s!ApiRP3wyITQrrh7rSG7YU9UfdLyZ

This doesn't appear to be a BOINC issue, as if I suspend one of the other tasks, it stops running. See https://1drv.ms/u/s!ApiRP3wyITQrrh1IrhVPs-ghspR-

Could you please investigate and see if this can be fixed.

Thanks

Yes. On my RPi also. It is strange and we try to understand why this happens. If this situation is critical, you can try to restart BOINC on your Pis.

Thanks for confirming that you're seeing this too.

It's not too big an issue, just means that I need to do a little more management.

I have same problem, but only if Boinc started from service. 32 bit Intel Atom N270, Linux Debian GNU/Linux 10 (buster) [4.19.0-16-686|libc 2.28 (Debian GLIBC 2.28-10)]
~ Suspend tasks failed to pause.
~ killall -SIGTSTP cmdock ...failed to pause.

Found a way to successfully pause. When I stop boinc-client service and manually run boinc as boinc user, then it is able to pause, both by suspend task and by SIGTSTP/SIGCONT signals. I guess something could be possibly wrong with 32 bit Debian 10 service blocks SIGTSTP signal or refuse to pause. My AMD64 Debian 11 Boinc service does not have this problem.

service boinc-client stop
su -l boinc -s /bin/bash
cd /var/lib/boinc-client
boinc & 

I may soon update my 32 bit to Debian 11 to see if this can fix boinc service fail to pause tasks issue.

I think this is a big issue on computers I also use for e.g. browsing, because I often forget to start BOINC after I stopped it. I had to stop receiving new tasks from SiDock@home on those computers and instead use yoyo@home. I still use SiDock on dedicated BOINC computers.

I reported my problems here:
https://www.sidock.si/sidock/forum_thread.php?id=198&postid=1614#1614

---