Hi

Since last macOS upgrade 26.5 (25F71) on my late 2020 Intel i9 iMac, Boinc (8.2.11) does not suspend the CPU tasks anymore : status of all tasks in boinc manager is suspended, but the process are still running and eating CPU. I could see that behaviour at least with Primegrid and NFS, I didn't test other projects so far.

$ ps aux | grep -i llr

boinc_project    60215   0,0  0,0 34279464   1564   ??  SN    1:53     0:28.33 srw_mac64_201105 --llr2 -c -oGerbicz=1 -oProofName=proof -oProofCount=128 -oProductName=prod -oPietrzak=1 -oCachePoints=0 -pSavePoints -q26732235*2^26732235-1 --nthreads 20

boinc_project    60217 1210,6  1,0 36458308 410652   ??  RN    1:53   4593:32.36 ../../projects/www.primegrid.com/llr2_1.3.0_mac64_220821 -oGerbicz=1 -oProofName=proof -oProofCount=128 -oProductName=prod -oPietrzak=1 -oCachePoints=0 -pSavePoints -q26732235*2^26732235-1 -d -t20 -oDiskWriteTime=1
jerome           68621   0,0  0,0 34272844    924 s000  S+    8:01     0:00.02 grep -i llr

I understand that the wrapper task is (S)uspended but the app itself is still (R)unning

GPU tasks are correctly suspended though.

The only simple solution I have is to stop the running client...

Strange isn't it ?


edit : also note that "sudo kill -STOP <pid>" on the unsuspended process is working, and if I wake up boinc from BM itself, the process is working again correctly (I don't need to use "sudo kill -CONT <pid>")

More strange now : after several days behaving like that it went back to normal, boinc suspension is effective on all tasks again. No change in boinc version or macOS neither.

Mystery will remain forever.

Mmm no it's not OK, I have problems to suspend boinc : sometimes it does, sometimes it won't. It only affects CPU tasks (any project), GPU task will always suspend / resume nicely.

Either with direct action (suspend activity) or automatic computer activity setup from boinc params : the first time suspension is requested (automatic or manual) it will work, then I resume and it crunches again, and then it becomes variable.

When this happens there is no way I can suspend boinc anymore, I'm forced to shut the client down. Once I restart it, I will have he 1st try ok, and then variability again.

I can’t say which combination of factors plays the biggest part, like time between suspend / resume, any other application running at the same time on the mac...

But I had never experienced this before : I clearly think this happened after upgrading to macOS 26.5, I have now upgraded to 26.5.1 after my initial post, no improvement.