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
This is detected by proper tests, the test calls STREAM API randomly without checking the callback events that the stream actually failed to start (async task). With default flags, failed to start the stream will not trigger stream_closed thus cause the stream leaks.
The solution in application are either
a. wait for {quic, start_completed, stream_handle(), #{is_peer_accepted := boolean()} } (QUIC_STREAM_EVENT_START_COMPLETE in msquic) to check if it is accepted or not.
b. set ?QUIC_STREAM_START_FLAG_SHUTDOWN_ON_FAIL when start the stream, so that you get event for stream shutdown
{quic, stream_closed, _, _}
and
{quic, send_shutdown_complete, _, _}
c. In NIF callback funs, we deref the stream handle so I will trigger stream close from application.
The text was updated successfully, but these errors were encountered: