You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In case process (gen_server) terminates with {stop, normal, ...} and the supervisor tries to stop it at the same time via terminate function, it's possible in rare cases to get:
To Reproduce
Create processes with a high rate, do self-termination and simultaneously terminate via supervisor.
Expected behavior
When a process terminates with a normal reason, the supervisor which tries to terminate it at the same time (monitors it), should get the real termination reason, not a 'noproc' reason.
…5201/OTP-17649' into maint-24
* Maria-12648430/supervisor_unlink_child_late/GH-5193/PR-5201/OTP-17649:
Keep supervisor children linked during shutdown
Describe the bug
In case process (gen_server) terminates with {stop, normal, ...} and the supervisor tries to stop it at the same time via terminate function, it's possible in rare cases to get:
see http://erlang.org/pipermail/erlang-questions/2021-September/101433.html
To Reproduce
Create processes with a high rate, do self-termination and simultaneously terminate via supervisor.
Expected behavior
When a process terminates with a normal reason, the supervisor which tries to terminate it at the same time (monitors it), should get the real termination reason, not a 'noproc' reason.
Affected versions
OTP-23.2.5
Additional context
http://erlang.org/pipermail/erlang-questions/2021-September/101433.html
The text was updated successfully, but these errors were encountered: