You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Assert failure in GC/API/GC/Collect_Aggressive_LargePages/Collect_Aggressive_LargePages.cmd #130432
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.
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.cmd
Error 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.cmd
Stack 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.
Activity
dotnet-policy-service commentedon Jul 9, 2026
Tagging subscribers to this area: @anicka-net, @dotnet/gc
See info in area-owners.md if you want to be subscribed.
JulieLeeMSFT commentedon Jul 9, 2026
gc-standalone GC/API tests crash on a native
pThreadassert via GCCoop::GCCoop.Other failures in the same test: OOM (#130302) and SIGSEGV (#130211).
JulieLeeMSFT commentedon Jul 9, 2026
Failed tests:
janvorli commentedon 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.
JulieLeeMSFT commentedon Jul 22, 2026
@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.cmd
Failed tests:
Error Message:
janvorli commentedon Jul 22, 2026
@JulieLeeMSFT that one is a timeout, so it is a different issue.
VincentBu commentedon Jul 28, 2026
Failed in: gc-standalone 20260726.1
Failed tests:
Error message:
Stack trace:
janvorli commentedon Aug 7, 2026
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.