Can you pastern the output from the task? You can get it from result status > error. I have a few low ram hosts, BOINC should wait on memory when you are low.

If I remember correctly (and it is quite possible that I do not) 'process got signal 11' means that the process has received an instruction to stop computation and exit, but does not provide much more detail than that. Its sort of a catch all thing that covers everything not covered by other stuff. Again, I could be totally wrong with this, so if I am someone please feel free to correct me.

Hello,
I must admit that I am not a real computer and linux specialist.
But I try to help you without warranty.

Let us assume, that it is a memory problem indeed.

There are two variables in BOINC settings.
One decides, how much memory can be used if the machine is busy.
The other decides, how much memory can be used if the machine is not busy.

Please set both variables to 100 per cent.
Additionally, please mark: Keep program in memory when paused.

Please note: I use the German language version, so I had to translate everything back into English. The descriptions in the BOINC settings might slightly differ form the words I have chosen.

Please give me feedback, whether the changes I proposed solved the problem or not.
Thank you.
M

Hello Mike,
I have chosen the option to leave the tasks in memory for years now (and this on
a fairly old computer and nothing bad happend.
There should be no reason to worry.
I whish you success and that the problem disappears.
Stay safe in these strange times, too.
Best whishes
Martin

Hello Mike,
my goal would be to get the problem really fixed.
Everything should be running fine all time.

Please look here:
https://boinc.mundayweb.com/wiki/index.php?title=Process_got_signal_11

It says:
This error can be caused by the infamous segmentation error (SIGSEGV error), meaning that something broke. be it your memory, virtual memory (page file) or it's a bad batch of tasks.

Check your system with memtest86+, make your page file anew, keep a tab on whether you're the only one returning these errors, or that others have them at the same time as well. If you are the only one, it's something on your system, if there are lots more, it's a bad batch of work.

But it can also happen when you use a 64bit operating system, while the project you're getting the crashes on only gives out 32bit applications (such as Einstein does). Installing the ia32 library package will fix this problem. See also process exited with code 22 which is a similar error, on the application level.




Let us think posiviely and suppose, that it is not a fragmenation error,

If this is the case, you can check, whether you are running a 64 bit or a 32 bit research application taking into account the following information:

Does World Community Grid offer a 64 bit version of the BOINC software?
No. Our recommended BOINC agents are those of the 32 bit variety because even though the client is 32 bit, it will run 64 bit applications. The agent does not do anything that requires 64 bit execution at this time, thus recommending a version that works on both makes life easier. The science applications are available in both 32 bit and 64 bit. A 64 bit science application can run on 32 bit BOINC client. The opposite is also true, a 32 bit science application can run on a 64 bit BOINC client.
Display similar help items
Return to Top

How do I know if my computer is running the 64-bit research application?

On a Windows machine, you can use the Windows task manager to view the process name. 64-bit research applications will end with "windows_intelx86_64", while 32-bit applications will end with "windows_intelx86"



On a Linux machine, you can find the PID of the research application (which will start with the name "wcg") and then execute the command "file -L /proc/PID/exe"

On OS X we only support 64 bit applications, therefore all World Community Grid tasks will be running a 64 bit application.


Maybe this new info helps
Best whishes
Martin