Ah, that's what I was afraid of, Ilian. Fortunately I've found a way around the problem. But at least one fracture point is now known. Thanks again for both your replies.
This is a message from the operating system, which has killed the process. The most typical scenario is severe memory starvation, for example, the Linux kernel has special OOM-Killer code to handle runaway processes.
