Test Failure: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd (OOM)

[JulieLeeMSFT]

Summary:
gc-standalone legs fail because the Helix machine cannot commit a ~3 GB GC region (E_OUTOFMEMORY) during coreclr_initialize; 13 work items.

Failed in (1):

• gc-standalone 20260705.1

Console Log: Console Log
Source: gc-standalone / coreclr windows x64 Checked gcstandalone @ Windows.10.Amd64.Open / GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd

Failed tests:

- coreclr linux arm64 Checked gcstandalone @ AzureLinux.3.Arm64.Open
- coreclr linux arm64 Checked gcstandaloneserver @ AzureLinux.3.Arm64.Open
- coreclr linux x64 Checked gcstandalone @ AzureLinux.3.Amd64.Open
- coreclr linux x64 Checked gcstandaloneserver @ AzureLinux.3.Amd64.Open
- coreclr windows x64 Checked gcstandalone @ Windows.10.Amd64.Open
- coreclr windows x64 Checked gcstandaloneserver @ Windows.10.Amd64.Open
  - GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd
  - GC/API/GC/GetConfigurationVariables/GetConfigurationVariables.cmd
  - GC/API/Refresh/Refresh/Refresh.cmd

Error Message:

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

Analysis:
Multiple gc-standalone work items (Collect_Aggressive_LargePages, GC/API/Refresh, GetConfigurationVariables, ...) abort before running with 'GC: Committing 3221225472 bytes for a region failed / GC heap initialization failed with error 0x8007000E / coreclr_initialize failed 0x8007000e'.
E_OUTOFMEMORY on a 3 GB region commit is a machine resource limitation (large pages / memory).
Issue #130211 tracks the SAME test (Collect_Aggressive_LargePages) but a DIFFERENT failure mode (SIGSEGV exit 139).

[dotnet-policy-service]

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