Repository navigation
Closed
Labels
GCStressarch-x86area-GC-coreclrdisabled-testThe test is disabled in source code against the issueThe test is disabled in source code against the issuein-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is mergedos-windows
Milestone
Description
Run: runtime-coreclr gcstress-extra 20221126.1
Failed test:
coreclr windows x86 Checked heapverify1 @ Windows.10.Amd64.Open
- GC\\Regressions\\Github\\Runtime_76219\\Runtime_76219\\Runtime_76219.cmd
Error message:
Assert failure(PID 876 [0x0000036c], Thread: 4844 [0x12ec]): Precondition failure: Illegal null pointerFAILED: ok
FAILED: CheckPointer(pv)
D:\a_work\1\s\src\coreclr\vm\ceemain.cpp, line: 1013
CORECLR! CHECK::Trigger + 0x256 (0x711dd930)
CORECLR! FilterStartupException + 0x20C (0x71303289)
CORECLR! EEStartup + 0x67 (0x71302355)
CORECLR! EH4_CallFilterFunc + 0x12 (0x7131a772)
CORECLR! except_handler4 + 0xD4 (0x71316724)
NTDLL! RtlConvertUlongToLargeInteger + 0xA2 (0x77ac3292)
NTDLL! RtlConvertUlongToLargeInteger + 0x74 (0x77ac3264)
NTDLL! KiUserExceptionDispatcher + 0xF (0x77ab0dbf)
CORECLR! WKS::gc_heap::gc1 + 0x689 (0x711b328d)
CORECLR! WKS::gc_heap::garbage_collect + 0x3B4 (0x711b2b79)
File: D:\a_work\1\s\src\coreclr\inc\check.h Line: 339
Image: C:\h\w\A5DC091E\p\corerun.exe
Return code: 1
Raw output file: C:\h\w\A5DC091E\w\AFA20916\uploads\Reports\GC.Regressions\Github\Runtime_76219\Runtime_76219\Runtime_76219.output.txt
Raw output:
BEGIN EXECUTION
"C:\h\w\A5DC091E\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" Runtime_76219.dll
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
Test Harness Exitcode is : 1
To run the test:
set CORE_ROOT=C:\h\w\A5DC091E\p
C:\h\w\A5DC091E\w\AFA20916\e\GC\Regressions\Github\Runtime_76219\Runtime_76219\Runtime_76219.cmd
Expected: True
Actual: False
Stack trace
at GC_Regressions._Github_Runtime_76219_Runtime_76219_Runtime_76219_._Github_Runtime_76219_Runtime_76219_Runtime_76219_cmd()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
Metadata
Metadata
Assignees
Labels
GCStressarch-x86area-GC-coreclrdisabled-testThe test is disabled in source code against the issueThe test is disabled in source code against the issuein-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is mergedos-windows
Type
Projects
- StatusShow more project fieldsNo status
Activity
EgorBo commentedon Nov 28, 2022
This test verifies that GC doesn't collect an unreferenced frozen object (that becomes referenced again then)
Apparently, it's broken with segments now, perhaps due to recent gc changes? (e.g. #78756). There were no changes related to frozen objects in VM/JIT recently
mangod9 commentedon Nov 28, 2022
@cshung as fyi..
cshung commentedon Nov 29, 2022
I took a look at the dump. Here are some high-level findings.
The test is run with these environment variables:
This is x86, so we are running Segments, not regions.
It is unrelated to Frozen Object Heap, as
SystemDomain::m_FrozenObjectHeapManagerisnull.I cannot reproduce it locally yet.
BruceForstall commentedon Dec 22, 2022
Another dup? #79807
v-wenyuxu commentedon Dec 23, 2022
Failed again in: runtime-coreclr gcstress-extra 20221221.1
Failed test:
Error message:
BruceForstall commentedon Jan 9, 2023
Another failure:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=129549&view=ms.vss-test-web.build-test-results-tab&runId=2799814&resultId=121108&paneView=debug
"coreclr OSX arm64 Checked jitstress_isas_nohwintrinsic"
@cshung There are lots of bugs for this test case and lots of different failures. Are you keeping the test enabled to collect more data, perhaps crash dumps? Or should we disable the test (for some appropriate subset of platforms) to clean the CI runs?
cshung commentedon Jan 9, 2023
Oh, I didn't realize this is actually running in CI. I thought this is a GCStress test case, let me move it out of the regular CI run for now.
7 remaining items
Reenable the GC/Regressions/Github/Runtime_76219 test (#131881)