The only time I've seen something like this, it was on a web hosting machine upon which there was a daemon watching resource utilization (CPU, memory, and time) and killing any processes that exceeded some predetermined thresholds. In that case, the fix was to abandon that web hosting provider.

2006-03-13 Retitled by planetscape, as per Monastery guidelines
Original title: 'Re: Terminated'