[ci-scan] Test failure: GC/API/GC/Collect_Aggressive_LargePages GC heap init fails with 0x8007000E
- Dominant language
- C#
- Stars
- 18.3k
- Forks
- 5.6k
- PR merge metrics
- PR metrics pending
Description
## Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1491722
Build error leg or test failing: coreclr Pri1 Runtime Tests Run GCStandAlone linux x64 checked @ azurelinux.3.amd64.open.rt - GC/API/GC/Collect_Aggressive_LargePages
Pipeline: `runtime-coreclr gc-standalone` (definition 146), branch `main`. The failure reproduces on the GCStandAlone linux x64 leg and persists into follow-up build [1494444](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1494444).
## Error Details
The `GC/API/GC/Collect_Aggressive_LargePages` test fails during runtime startup: the GC cannot commit a 3 GiB (0xC0000000) region for the configured large-pages heap, so `coreclr_initialize` aborts with `E_OUTOFMEMORY` (0x8007000E) and the test harness records exit code 255 against an expected 100. This is a distinct failure signature from the SIGSEGV / exit-139 manifestation of the same test tracked in dotnet/runtime#130211.
```
Running test: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd
GC: Committing 3221225472 bytes for a region failed
GC heap initialization failed with error 0x8007000E
BEGIN: coreclr_initialize failed - Error: 0x8007000e
END: coreclr_initialize failed - Error: 0x8007000e
Expected: 100
Actual: 255
END EXECUTION - FAILED
Xunit.Sdk.TrueException: GC: Committing 3221225472 bytes for a region failed
```
## Error Message
```json
{
"ErrorMessage": [
"GC: Committing 3221225472 bytes for a region failed",
"GC heap initialization failed with error 0x8007000E"
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
```
## First build it occurred
Earliest occurrence of this heap-init OOM signature in the scanned window is build [1470804](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1470804) (2026-06-18); the immediately preceding build [1466400](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1466400) (2026-06-16) does not contain it. The signature then recurs continuously through source build [1491722](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1491722) (2026-07-02) and follow-up build [1494444](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1494444) (2026-07-05).
## Duplicate search
Searched open and closed `Known Build Error` issues for `Collect_Aggressive_LargePages`, `GC heap initialization failed`, and `0x8007000E`: no existing KBE matches this heap-init OOM signature. Related: dotnet/runtime#130211 tracks the same test on the same leg failing with a SIGSEGV (exit 139); that issue's signature (`Collect_Aggressive_LargePages.sh: line 248:` plus a segfault) does not appear in this exit-255 heap-init OOM log, so Build Analysis will not auto-associate the two. Both share first-occurrence build 1470804 and are likely the same broken large-pages GC test manifesting with different exit codes.
---
Filed by the CI outer-loop failure scanner (detection only). Mitigation — a fix PR or owner hand-off — is handled by the companion `ci-failure-fix` workflow, which walks open `[ci-scan]` KBEs.
> [!NOTE]
> This issue was generated with the assistance of GitHub Copilot (AI). Signatures and build references were verified against public AzDO / Helix logs.
> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `dotnet.github.io`
>> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "dotnet.github.io"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>
> [!NOTE]
>
> 🔒 Integrity filter blocked 20 items
>
> The following items were blocked because they don't meet the GitHub integrity level.
>
> - [#86273](https://github.com/dotnet/runtime/issues/86273) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#114222](https://github.com/dotnet/runtime/issues/114222) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#127571](https://github.com/dotnet/runtime/pull/127571) `search_pull_requests`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#130289](https://github.com/dotnet/runtime/issues/130289) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#7096](https://github.com/dotnet/runtime/issues/7096) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5984](https://github.com/dotnet/runtime/issues/5984) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5158](https://github.com/dotnet/runtime/issues/5158) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5637](https://github.com/dotnet/runtime/issues/5637) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5101](https://github.com/dotnet/runtime/issues/5101) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#44158](https://github.com/dotnet/runtime/issues/44158) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5318](https://github.com/dotnet/runtime/issues/5318) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#7231](https://github.com/dotnet/runtime/issues/7231) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#5130](https://github.com/dotnet/runtime/issues/5130) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#129960](https://github.com/dotnet/runtime/issues/129960) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#55803](https://github.com/dotnet/runtime/issues/55803) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - [#71338](https://github.com/dotnet/runtime/issues/71338) `search_issues`: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
> - ... and 4 more items
>
> To allow these resources, lower `min-integrity` in your GitHub frontmatter:
>
> ```yaml
> tools:
> github:
> min-integrity: approved # merged | approved | unapproved | none
> ```
>
>
> Generated by [CI Outer-Loop Failure Scanner](https://github.com/dotnet/runtime/actions/runs/28869475338/agentic_workflow) · ● 18M · [◷](https://github.com/search?q=repo%3Adotnet%2Fruntime+is%3Aissue+%22gh-aw-workflow-call-id%3A+dotnet%2Fruntime%2Fci-failure-scan%22&type=issues)
### Report
|Build|Repository|Test|Pull Request|
|---|---|---|---|
|[1594615](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1594615)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1594615&view=ms.vss-test-web.build-test-results-tab&runId=44020868&resultId=103259)||
|[1590860](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1590860)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1590860&view=ms.vss-test-web.build-test-results-tab&runId=43916716&resultId=101435)||
|[1587258](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1587258)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1587258&view=ms.vss-test-web.build-test-results-tab&runId=43805892&resultId=103134)||
|[1584864](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1584864)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1584864&view=ms.vss-test-web.build-test-results-tab&runId=43730766&resultId=102150)||
|[1580816](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1580816)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1580816&view=ms.vss-test-web.build-test-results-tab&runId=43612562&resultId=103471)||
|[1574173](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1574173)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1574173&view=ms.vss-test-web.build-test-results-tab&runId=43379010&resultId=103208)||
|[1570365](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1570365)|dotnet/runtime|[GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1570365&view=ms.vss-test-web.build-test-results-tab&runId=43246938&resultId=103107)||
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|3|7|
Contributor guide
Research direction
Start with GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd and reproduce it on the GCStandAlone linux x64 checked Azure Linux leg. Compare the first failing build 1470804 with 1466400 and inspect the linked build logs for the 3 GiB commit failure. Done means the test completes without GC heap initialization failing and reports its expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux
- Domain
- ci-cd, operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100