[erlang-questions] Strange interaction between Docker and Erlangs ports (exit_status lost)

André Cruz andre@REDACTED
Fri Dec 18 00:00:37 CET 2015

Sent from my iPad

> On 17/12/2015, at 21:33, Lukas Larsson <garazdawi@REDACTED> wrote:
> Looking a bit more on the internet i found this: https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/ which seems to describe exactly the problem that you are experiencing. The erlang vm is not built to run as the pid 1 process, even with my new changes in the master branch this will still be a problem as instead of missing out on exit_status messages you will have a system full of zombie processes.

I understand that orphaned processes will be left as zombies, but that is a more explicit problem. You list the processes and see them. The Beam VM being stuck forever because the message we know we should have received is lost is a much more confusing situation and it took a few people before we even realized what the problem was. There are several reports in the wild of strange lock ups when compiling Elixir code, for example, that I think are related to this. So, in conclusion, it would be nice if the VM simply discarded unknown SIGCHLDS that it happens to waitpid() upon without discarding the correct SIGCHLD and sending the expected exit_status message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20151217/518c0dfa/attachment.htm>

More information about the erlang-questions mailing list