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.

Sign up for GitHub

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

Jump to bottom

Test run hang in PipeReader.ReadAsync #387

Open

AArnott opened this issue Sep 2, 2021 · 1 comment

Labels

bug

Collaborator

AArnott commented Sep 2, 2021 •

edited

Loading

This pipeline hung after running tests, waiting on this "stack" of async tasks:

0000020b0e067ce0 00007ffa567dd9d8      152          0 Nerdbank.Streams.MultiplexingStream+V2Formatter+<DisposeAsync>d__5
0000020b0e067d78 00007ffa567ddd68      152          1 Nerdbank.Streams.MultiplexingStream+<DisposeAsync>d__55
0000020b0e067e10 00007ffa56866620      128          0 MultiplexingStreamTests+<DisposeAsync>d__9

The formatter was waiting on the read semaphore:
https://github.com/AArnott/Nerdbank.Streams/blob/db117800aedfae7ae2624e89203179c7a29dcaf3/src/Nerdbank.Streams/MultiplexingStream.Formatters.cs#L292

The text was updated successfully, but these errors were encountered:

AArnott added the bug label

Collaborator Author

AArnott commented Sep 9, 2021

The sequence file indicates that MultiplexingStreamV3Tests.CommunicateOverOneChannel never completed.

AArnott mentioned this issue

System.IO.Pipelines.Pipe.ReadAsync fails to cancel on CancellationToken dotnet/runtime#58909

Closed

AArnott changed the title ~~Test run hang, suggesting a real product bug in MultiplexingStream~~ Test run hang in PipeReader.ReadAsync

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