Hi,

I loose 3 WU (+7 hours, +4 hours, ~2 hours)
WU 1 - WU 2 - WU 3

all killed with SIGSEGV (11): Invalid memory reference

I found this on SIGSEGV

QUESTION
Signal 11, what does that mean?
ANSWER
Signal 11, or officially know as "segmentation fault", means that the program accessed a memory location that was not assigned. That's usually a bug in the program. So if you're writing your own program, that's the most likely cause. However, this FAQ will concentrate on the possibilities besides that.

About the context.

When I've checked the running processes before the application crash, yafu wasn't running but gnfs-lasieve.

I checked the processes because my computer has become slow.

I found that the memory get low. I run also yoyo/ecm project and nfs@home. I had 2 yoyo/ecm running, 1 nfs@home and 3 yafu/gnfs-lasieve running/in memory.

The memory (4GB) was use almost at 100% (3700 MB on 3888 MB) and the swap was used intensively (2500-3500 MB on 4700 MB)

So I suspect a problem in gnfs-lasieve with bad memory condition.

I change the memory settings in the projects (to use 50% memory and 75% swap).
Will see if it's better.

Regards

Ludo

This is a common problem of nearly each application, that the app crashes on low memory. The app allocates memory and in most cases it isn't checked if this was done. In low memory conditions somtimes just NULL is returned. But afterwards the app access this pointer and crashes.
yoyo