-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Premature connection close #55903
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsCollected from different comments on different issues: Saw something similar on stream today
Originally posted by @wfurt in #53224 (comment)
|
Seeing one of the crashes again:
I ran S.N.Http tests in a loop, it crashed on 79th run. I've had these tests locally re-enabled: HttpClientHandlerTest_Http3.ClientSettingsReceived_Success
HttpClientHandlerTest_Http3.SendStreamLimitRequestsConcurrently_Succeeds
HttpClientHandlerTest_Http3.SendMoreThanStreamLimitRequestsConcurrently_LastWaits |
This seems like it's one of the issues we identified in the code review -- specifically that we call TryAddStream too late, here: https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/MsQuicStream.cs#L119 It seems like we should call TryAddStream before we call the MsQuicStream constructor. And we shouldn't throw if it fails, we should just close the stream, since this indicates that the connection is shut down. This may not completely fix the issue, but it would at least get us past the assertion. And we should never be throwing like this in a callback anyway. |
I'm not sure if moving |
Triage: we haven't seen this is a while, but it might be just due to multitude of disabled tests. |
Collected from different comments on different issues:
Stream open fails with INVALID_STATE
Saw something similar on stream today
@wfurt According to msquic code https://github.com/microsoft/msquic/blob/3898b2b88085a478eeb844885ea78daa9b060d06/src/core/stream.c#L207-L211:
Your error means the connection is closed. It just looks like another symptom of premature connection close, reported in this comment #55380 (comment)
Native crash
While diffing through, I founds another crashing pattern:
the lock seems to be all empty.
Managed crash
Got different exception, this time managed one:
The text was updated successfully, but these errors were encountered: