[erlang-questions] Monitor limitations

Siri Hansen erlangsiri@REDACTED
Mon Mar 24 17:37:35 CET 2014

>From the notes in the ticket:

"Some analysis yields that the cause is that the gen_server:start() call
ends up in erlang:spawn_opt(..., [monitor]) which return {Pid, Monitor},
making the proc_lib:sync_wait() wait for {Pid, Monitor} and not Pid
which is what the newly spawned process sends in the ack-message."

I haven't investigated further, so I don't know anything more about it. It
doesn't seem too hard to solve, though, so it seems strange that the
solution was to throw a badarg. Or maybe I missed something crucial...


2014-03-22 11:44 GMT+01:00 Michał Ptaszek <erlang@REDACTED>:

> Hey everyone,
> can anyone please shed some more light on OTP-6345?
> For some reasons we can not atomically spawn processes with
> proc_lib:spawn_opt with 'monitor' flag. The same problem happens with
> erlang:spawn_opt/5 where we can not spawn a remote process with 'monitor'
> (however linking is totally ok).
> Thanks,
> Michal
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140324/ba86f2ee/attachment.htm>

More information about the erlang-questions mailing list