[ci-scan] Test failure: PInvokeUnhandled consistency check assert in runtime-interpreter

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1434343
Build error leg or test failing: windows x64 Checked interpreter - baseservices/exceptions/UnhandledExceptionHandler/PInvoke/PInvokeUnhandled/PInvokeUnhandled.cmd

Error Details

The PInvokeUnhandled test fails in runtime-interpreter (def 316) on Windows under CoreCLR interpreter mode. When the unhandled exception path triggers a stack walk, the StackFrameIterator encounters a frame where the internal consistency check (GetRegdisplaySP(m_crawl.pRD) == (TADDR)pICF->GetCallSiteSP()) || (GetFP(m_crawl.pRD->pCurrentContext) == pICF->GetCalleeSavedFP()) fails. This is an interpreter-mode stack-walker incompatibility when handling unhandled exceptions via P/Invoke.

Affected pipelines:

• runtime-interpreter (def 316): windows x64 Checked, windows arm64 Checked
• Confirmed in builds: 1434343 (2026-05-25), 1431519 (2026-05-22), 1428137 (2026-05-20) — persistent across the entire scanned window (10 consecutive failures).

Related KBE: dotnet#127899 (similar interpreter stack-walk issue with m_crawl.GetCodeInfo()->IsValid() assertion in stackoverflow handling).

Assert failure(PID 19300 [0x00004b64], Thread: 11724 [0x2dcc]): Consistency check failed:
FAILED: (GetRegdisplaySP(m_crawl.pRD) == (TADDR)pICF->GetCallSiteSP()) || (GetFP(m_crawl.pRD->pCurrentContext) == pICF->GetCalleeSavedFP())

CORECLR! CHECK::Trigger + 0x1E8

Expected: 100
Actual: -1073740286
END EXECUTION - FAILED

Error Message

{
  "ErrorMessage": ["PInvokeUnhandled", "Consistency check failed", "GetRegdisplaySP(m_crawl.pRD) == (TADDR)pICF->GetCallSiteSP()"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

First build it occurred

• Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1407440
• Finished: 2026-05-04
• Persistent across the entire scanned window; true origin may predate 2026-05-04.

Note

This issue was generated by the CI Outer-Loop Failure Scanner.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #88582 search_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:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 25.7M · ◷