[erlang-questions] Who is killing my process?

[Mihai Balea]

On May 18, 2010, at 1:13 PM, Rapsey wrote:

> Are you updating your code? Processes are killed when they're running old
> code and it gets updated.

Yes, it turned out that was the case...a bunch of workers would be spawned for a specific job, and workers would load the latest version of the job callback module. If a worker had a chance to start working while another was still initializing, it would result in a code purge from under the first worker.

Anyway, simply ensuring the code is loaded once before the workers are spawned solved the problem.

Thanks,

Mihai