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
[erts] Make sure nosuspend command signals to ports are handled properly
No-suspend port command signals (i.e. port command signals sent using the
`erlang:port_command/3` BIF or the `erlang:send/3` BIF with the `nosuspend`
option) were not aborted properly in all scenarios which could leave the
port queue in a busy state indefinitely. Asynchronously sent no-suspend command
signals (i.e, port command signals sent using the `erlang:send/3` BIF with the
`nosuspend` option) could sometimes be delivered even though the port was busy.
0 commit comments