-
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
[tvOS] OutOfMemoryException in System.IO.Pipelines.Tests.PipeWriterTests.CompleteWithLargeWriteThrows #64930
Comments
Tagging subscribers to 'os-tvos': @steveisok, @akoeplinger Issue DetailsRunfo Tracking Issue: OutOfMemoryException in System.IO.Pipelines.Tests.PipeWriterTests.CompleteWithLargeWriteThrows
Build Result Summary
|
3 of the last 5 rolling builds have hit this. @steveisok / @akoeplinger any ideas on who might be able to investigate what is going on here? |
Yes, we'll take a look at it. Seems contention related - maybe allocate a smaller amount in runtime/src/libraries/System.IO.Pipelines/tests/PipeWriterTests.cs Lines 233 to 258 in 99452b2
|
Looks like we're occasionally hitting |
|
Allocate the buffer outside of the loop so we don't hit OOM issues. While looking at the test I noticed that it actually had a bug too: Nothing was asserting that we indeed throw an InvalidOperationException when the writer is completed. Adding `Assert.ThrowsAsync` revealed that the current loop iteration count was too low to hit the exception reliably within the 10ms delay so instead check for the execution time. Fixes dotnet#64930
Allocate the buffer outside of the loop so we don't hit OOM issues. While looking at the test I noticed that it actually had a bug too: Nothing was asserting that we indeed throw an InvalidOperationException when the writer is completed. Adding `Assert.ThrowsAsync` revealed that the current loop iteration count was too low to hit the exception reliably within the 10ms delay so instead check for the execution time. Fixes #64930
Runfo Tracking Issue: OutOfMemoryException in System.IO.Pipelines.Tests.PipeWriterTests.CompleteWithLargeWriteThrows
Build Result Summary
The text was updated successfully, but these errors were encountered: