Repository navigation
Assert failure in GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd #130432
Description
Activity
- addedKnown Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tab
on Jul 9, 2026 - addeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Jul 9, 2026 dotnet-policy-service commented
on Jul 9, 2026 ContributorMore actionsTagging subscribers to this area: @anicka-net, @dotnet/gc
See info in area-owners.md if you want to be subscribed.- addedblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
on Jul 9, 2026 Failed tests:
- coreclr windows arm64 Checked gcstandaloneserver @ Windows.11.Arm64.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
- removeduntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
on Jul 14, 2026 These issues are all in gc-standalone pipeline. I can repro it locally. The GC initialization fails in case large pages are requested with GC in segments mode.
@janvorli, is this the same error? It failed in naot outerloop.
Failed in (1):
Console Log: Console Log
Source: runtime-nativeaot-outerloop / coreclr windows x64 Checked @ Windows.10.Amd64.Open / GC\API\GC\Collect_Aggressive_LargePages\Collect_Aggressive_LargePages.cmdFailed tests:
- coreclr windows x64 Checked @ Windows.10.Amd64.Open - GC\API\GC\Collect_Aggressive_LargePages\Collect_Aggressive_LargePages.cmdError Message:
call C:\h\w\ADFF0973\p\nativeaottest.cmd C:\h\w\ADFF0973\w\95310865\e\GC\API\GC\Collect_Aggressive_LargePages\ Collect_Aggressive_LargePages.dll Expected: 100 Actual: -1 END EXECUTION - FAILED@JulieLeeMSFT that one is a timeout, so it is a different issue.
Reacted by Julie LeeFailed in: gc-standalone 20260726.1
Failed tests:
coreclr windows arm64 Checked gcstandaloneserver @ Windows.11.Arm64.Open - GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd coreclr windows x64 Checked gcstandaloneserver @ Windows.10.Amd64.Open - GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmdError message:
Assert failure(PID 8460 [0x0000210c], Thread: 8940 [0x22ec]): pThread CORECLR! GCCoop::GCCoop + 0x50 (0x00007ff9`64b83000) CORECLR! CLRLastThrownObjectException::Validate + 0x3C (0x00007ff9`64ef13ec) CORECLR! `EEStartupHelper'::`1'::catch$8 + 0x84 (0x00007ff9`651e4104) CORECLR! CallSettingFrame + 0x68 (0x00007ff9`64b65b80) CORECLR! _FrameHandler3::CxxCallCatchBlock + 0x1C0 (0x00007ff9`650b9200) <no module>! <no symbol> + 0x0 (0x733efff9`93d33178) File: D:�_work1ssrccoreclr�m hreads.inl:44 Image: C:hwAAEB0999pcorerun.exe Return code: 1 Raw output file: C:hwAAEB0999w9E130886uploadsAPIGCCollect_Aggressive_LargePagesoutput.txt Raw output: BEGIN EXECUTION "C:hwAAEB0999pcorerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true" Collect_Aggressive_LargePages.dll Expected: 100 Actual: -1073740286 END EXECUTION - FAILED FAILED Test Harness Exitcode is : 1 To run the test: Set up CORE_ROOT and run. > C:hwAAEB0999w9E130886eGCGC../API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmdStack trace:
at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 135 at Program.<<Main>$>g__TestExecutor24|0_25(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)The test is incompatible with GC segments mode which we test in the gc-standalone leg, because it sets the DOTNET_GCHeapHardLimit and DOTNET_GCLargePages together and that combination cannot work with segments.
I'll leave the issue open until the gc-standalone leg is really suspended.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsNo status
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1501377
Build error leg or test failing: GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd
Error Message
Fill the error message using step by step known issues guidance.
{ "ErrorPattern": "CORECLR! GCCoop::GCCoop \\+.+\\(.+\\)", "BuildRetry": false, "ExcludeConsoleLog": false }Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1501377
Error message validated:
[CORECLR! GCCoop::GCCoop \+.+\(.+\)]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/9/2026 8:59:41 PM UTC
Report
Summary