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
If the remote peer closes a connection, on_close() will be called because recv returns 0, but the socket associated with the flow is never closed.
If the event loop is stopped via e.g. a signal handler, and neat_free_ctx() is called afterwards, all open sockets are closed, but on_close() is not called for the respective flows. This results in userData associated with the flows not being freed.
I am pretty sure issue 1 is a bug, but I am not sure if issue 2 is a bug.
The text was updated successfully, but these errors were encountered:
I experience two issues when flows are closed:
on_close()
will be called becauserecv
returns 0, but the socket associated with the flow is never closed.neat_free_ctx()
is called afterwards, all open sockets are closed, buton_close()
is not called for the respective flows. This results inuserData
associated with the flows not being freed.I am pretty sure issue 1 is a bug, but I am not sure if issue 2 is a bug.
The text was updated successfully, but these errors were encountered: