镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

[HTTP/3] [HttpStress] QuicException: Stream aborted by peer (258) in (POST Duplex | PUT) Slow #100534

Closed

Description

@antonfirsov

There are 30-50 hits per Linux CI run since #100023, and some rare sporadic Windows hits, but with error code 269.

System.Net.Http.HttpRequestException: Error while copying content to a stream.
 ---> System.Net.Http.HttpProtocolException: The HTTP/3 server reset the stream. HTTP/3 error code 'H3_INTERNAL_ERROR' (0x102). (HttpProtocolError)
 ---> System.Net.Quic.QuicException: Stream aborted by peer (258).
   at System.Net.Quic.ResettableValueTaskSource.TryComplete(Exception exception, Boolean final) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/Internal/ResettableValueTaskSource.cs:line 177
   at System.Net.Quic.ResettableValueTaskSource.TrySetException(Exception exception, Boolean final) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/Internal/ResettableValueTaskSource.cs:line 237
   at System.Net.Quic.QuicStream.HandleEventPeerSendAborted(_PEER_SEND_ABORTED_e__Struct& data) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicStream.cs:line 580
   at System.Net.Quic.QuicStream.HandleStreamEvent(QUIC_STREAM_EVENT& streamEvent) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicStream.cs:line 635
   at System.Net.Quic.QuicStream.NativeCallback(QUIC_HANDLE* stream, Void* context, QUIC_STREAM_EVENT* streamEvent) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicStream.cs:line 667
--- End of stack trace from previous location ---
   at System.Net.Quic.ResettableValueTaskSource.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/Internal/ResettableValueTaskSource.cs:line 251
   at System.Net.Quic.QuicStream.ReadAsync(Memory`1 buffer, CancellationToken cancellationToken) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicStream.cs:line 308

Activity

  1. added this to the 9.0.0 milestone on Apr 2, 2024
  2. dotnet-policy-service commented on Apr 2, 2024

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @dotnet/ncl
    See info in area-owners.md if you want to be subscribed.

  3. ManickaP commented on Apr 3, 2024

    @ManickaP
    Member

    This might be the very same root cause as #76183 (comment)

  4. self-assigned this
    on Apr 4, 2024
  5. added
    tracking-external-issueThe issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly
    on Jun 26, 2024
  6. locked and limited conversation to collaborators on Aug 9, 2024
  7. antonfirsov commented on Aug 20, 2024

    @antonfirsov
    ContributorAuthor

    There were recent occurrences, reopening. Even though the root cause might be the same as for #76183, it's worth to track the issue separately.

  8. modified the milestones: 9.0.0, 10.0.0 on Oct 22, 2024
  9. removed
    tracking-external-issueThe issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly
    on Oct 22, 2024
  10. modified the milestones: 10.0.0, 9.0.0 on Oct 22, 2024
  11. added
    tracking-external-issueThe issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly
    on Oct 22, 2024
  12. ManickaP commented on Oct 22, 2024

    @ManickaP
    Member

    I see only error code 267 request_rejected, I'll close this one, because what we're seeing is covered by #109121.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-System.Net.Httptracking-external-issueThe issue is caused by external problem (e.g. OS) - nothing we can do to fix it directly

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions