Not even a single task is finishing without an error on my computer. As far as I looked into stderr outputs all tasks are getting the signal 11 and they don't even do anything else.
I suspended fetching work units until further notice. Too bad, I haven't discovered this behaviour at an earlier point.

Not even a single task is finishing without an error on my computer. As far as I looked into stderr outputs all tasks are getting the signal 11 and they don't even do anything else.
I suspended fetching work units until further notice. Too bad, I haven't discovered this behaviour at an earlier point.

Looking through recent Mac results I found several other Mac users having the same problem, but the majority were fine. The ones getting the signal 11 all had Darwin OS version 11.4.2 or earlier. Also, all the good results were from Darwin version 12.6.0 or higher.

I'm not that familiar with the various Mac OS versions, but that seems to be the root cause of this. If it's not an inconvenience, you could try to upgrade your OS. If you decide to do that, please let me know if it fixes the problem.

And thanks for bringing this to my attention!

Interestingly the same happens to all tasks of the CSG but not to any other project offering CPU work units for OSX computers.

Interestingly the same happens to all tasks of the CSG but not to any other project offering CPU work units for OSX computers.

My guess is that it's related to the version of the build tools and/or OS used to build the apps. Since I don't have a mac, I use a virtual machine, so I am kind of stuck with the OS version that came with it (Mountain Lion).

Again, I'm not that familiar with the Mac OS, but it appears that any OS predating Mountain Lion (12.0.0) may have problems running NumberFields@home.