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
Under CFG (Control Flow Guard) mode in runtime-coreclr jit-cfg (definition 155), the Loader and Regressions work items crash with a GC object validation assertion. The Object::ValidateInner function detects a corrupted OBJECTREF during GC enumeration of live slots, indicating a GC hole where a register or stack slot that GcInfo reports as containing an object reference actually holds corrupted data.
Affected tests include classloader/explicitlayout/objrefandnonobjrefoverlap/case13 and Regressions/coreclr/25057/byref/byref.dll.
runtime-coreclr jit-cfg (def 155): windows x64 checked, windows arm64 checked
First build it occurred:Build 1452746 (June 7, 2026). Prior build 1442662 (June 1) succeeded. 6 consecutive failures in window.
Related issues:#129545, #129546 (same GC validation asserts in Loader tests under gcstress)
Error Message
{
"ErrorMessage": ["Detected use of a corrupted OBJECTREF. Possible GC hole.", "Object::ValidateInner"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Note
🔒 Integrity filter blocked 13 items
The following items were blocked because they don't meet the GitHub integrity level.
#84911search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#95367search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#108070search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#114229search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#112196search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#129682search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#128330search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#126819search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#115319search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#91975search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#114222search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#116358search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#86273search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1474087
Build error leg or test failing: coreclr Pri1 Runtime Tests Run windows x64 checked-Loader.2.3
Error Details
Under CFG (Control Flow Guard) mode in
runtime-coreclr jit-cfg(definition 155), the Loader and Regressions work items crash with a GC object validation assertion. TheObject::ValidateInnerfunction detects a corrupted OBJECTREF during GC enumeration of live slots, indicating a GC hole where a register or stack slot that GcInfo reports as containing an object reference actually holds corrupted data.Affected tests include
classloader/explicitlayout/objrefandnonobjrefoverlap/case13andRegressions/coreclr/25057/byref/byref.dll.Affected pipelines:
First build it occurred: Build 1452746 (June 7, 2026). Prior build 1442662 (June 1) succeeded. 6 consecutive failures in window.
Related issues: #129545, #129546 (same GC validation asserts in Loader tests under gcstress)
Error Message
{ "ErrorMessage": ["Detected use of a corrupted OBJECTREF. Possible GC hole.", "Object::ValidateInner"], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Note
🔒 Integrity filter blocked 13 items
The following items were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Report
Summary