Repository navigation
MemoryStream_CapacityBoundaryChecks fails with OutOfMemoryException #119839
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1151114
Build error leg or test failing: MemoryStream_CapacityBoundaryChecks
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "[FAIL] System.IO.Tests.MemoryStreamTests.MemoryStream_CapacityBoundaryChecks",
"BuildRetry": false,
"ExcludeConsoleLog": false
}The test failed for me even locally on Windows (the build above is on Android). The exact failure is:
Assert.Throws() Failure: Exception type was not an exact match
Expected: typeof(System.ArgumentOutOfRangeException)
Actual: typeof(System.OutOfMemoryException)
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1151114
Error message validated: [Expected: typeof(System.ArgumentOutOfRangeException)]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/18/2025 9:43:39 AM UTC
Report
| Build | Definition | Test | Pull Request |
|---|---|---|---|
| 1151853 | dotnet/runtime | System.Numerics.Tests.modpowTest.RegressionIssuePerformance2575 | #119846 |
| 1151627 | dotnet/runtime | System.IO.Tests.WorkItemExecution | |
| 1151114 | dotnet/runtime | System.IO.Tests.WorkItemExecution |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 3 | 3 |
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1151114
Error message validated: [MemoryStream_CapacityBoundaryChecks Expected: typeof(System.ArgumentOutOfRangeException)]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 9/18/2025 5:15:01 PM UTC
Report
| Build | Definition | Test | Pull Request |
|---|---|---|---|
| 1151853 | dotnet/runtime | System.Numerics.Tests.modpowTest.RegressionIssuePerformance2575 | #119846 |
| 1151627 | dotnet/runtime | System.IO.Tests.WorkItemExecution | |
| 1151114 | dotnet/runtime | System.IO.Tests.WorkItemExecution |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 3 | 3 |
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 16 | 48 |
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1151114
Error message validated: [[FAIL] System.IO.Tests.MemoryStreamTests.MemoryStream_CapacityBoundaryChecks]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/8/2025 7:34:34 AM UTC
Report
| Build | Definition | Test | Pull Request |
|---|---|---|---|
| 1151853 | dotnet/runtime | System.Numerics.Tests.modpowTest.RegressionIssuePerformance2575 | #119846 |
| 1151627 | dotnet/runtime | System.IO.Tests.WorkItemExecution | |
| 1151114 | dotnet/runtime | System.IO.Tests.WorkItemExecution |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 3 | 3 |
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 16 | 48 |
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Activity
dotnet-policy-service commentedon Sep 19, 2025
Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.
vitek-karas commentedon Oct 1, 2025
Likely would be "fixed" if we implemented dotnet/xharness#1473
matouskozak commentedon Oct 8, 2025
I've updated the error messge to
[FAIL] System.IO.Tests.MemoryStreamTests.MemoryStream_CapacityBoundaryChecksas the previous one didn't catch all the errors on the CI. Sometimes we getor
janvorli commentedon Nov 26, 2025
I think runtime throws a wrong exception. It comes from this place in the
AllocateSzArray:runtime/src/coreclr/vm/gchelpers.cpp
Lines 640 to 641 in 8bfc105
I believe array allocation should throw
ArgumentOutOfRangeExceptionas the test checks when the requested size is larger than the maximum index. TheOutOfMemoryExceptionshould be thrown only when the requested size is in range, but the allocation failed.@jkotas am I right?
jkotas commentedon Nov 26, 2025
This has thrown OutOfMemoryException with a custom message since forever. Changing it would be a breaking change.
I believe that this failure was introduced by #119089 and fixed by #120091. We are not seeing any more hits:
Closing