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
Windows x86 cDAC GC-reference stress misses an interior reference in the active PrestubMethodFrame while running the NotYetLoadedArgType debuggee. The remaining 19 frames agree with the runtime.
Reproduction Steps
Observed in runtime-diagnostics build 1620305, windows-x86 release CdacStressTest, in Microsoft.Diagnostics.DataContractReader.Tests.GCStress.CdacStressTests.GCRefStress_AllVerificationsPass for NotYetLoadedArgType.
The uploaded debuggee log contains two such failed verifications. The work-item console includes one in its bounded failure excerpt. No deterministic local reproduction has been established.
Expected behavior
The cDAC reports the same interior reference from the active prestub frame as the native runtime.
Actual behavior
The runtime reports 94 references and the cDAC reports 93. Frame 0 is a PrestubMethodFrame with cDAC=0 RT=1; every other frame matches.
Regression?
The introducing change is not identified. This is a distinct signature from the EventSource cDAC=7 RT=47 mismatch previously observed on main. An independent main-branch occurrence of this specific prestub mismatch has not been confirmed.
The reporting PR only adds Wasm GC-info traits/registration and a separate unit-test fixture; the failing Windows x86 decoder and frame-scanning implementation are unchanged by it.
Known Workarounds
None established.
Configuration
Windows x86 runtime, Release, cDAC GC-reference stress, NotYetLoadedArgType debuggee. The Helix host queue is Windows x64.
Other information
This issue deliberately matches only the missing prestub-frame root, not every stress-test failure. Root cause is still open; the log indicates an interior reference (Flags=0x1).
Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
Build Analysis parses only the single JSON block under Error Message.
ErrorPattern uses .NET Singleline | IgnoreCase | NonBacktracking matching with a 50ms-per-line timeout.
Keep the regex anchored, prefer [^\n]* instead of .*, and avoid catastrophic backtracking.
Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log
The anchored pattern was verified against the failing Helix console; no passing or skipped line matches. Only the volatile frame address is generalized.
Note
Prepared with GitHub Copilot.
Known issue validation
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=1620305 Error message validated:[^\s*Frame #0 <frame PrestubMethodFrame 0x[0-9a-f]+> \[MISMATCH\] cDAC=0 RT=1\b] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 10/2/2026 9:10:13 AM UTC
Description
Windows x86 cDAC GC-reference stress misses an interior reference in the active
PrestubMethodFramewhile running theNotYetLoadedArgTypedebuggee. The remaining 19 frames agree with the runtime.Reproduction Steps
Observed in runtime-diagnostics build 1620305,
windows-x86 release CdacStressTest, inMicrosoft.Diagnostics.DataContractReader.Tests.GCStress.CdacStressTests.GCRefStress_AllVerificationsPassforNotYetLoadedArgType.The uploaded debuggee log contains two such failed verifications. The work-item console includes one in its bounded failure excerpt. No deterministic local reproduction has been established.
Expected behavior
The cDAC reports the same interior reference from the active prestub frame as the native runtime.
Actual behavior
The runtime reports 94 references and the cDAC reports 93. Frame 0 is a
PrestubMethodFramewithcDAC=0 RT=1; every other frame matches.Regression?
The introducing change is not identified. This is a distinct signature from the EventSource
cDAC=7 RT=47mismatch previously observed on main. An independent main-branch occurrence of this specific prestub mismatch has not been confirmed.The reporting PR only adds Wasm GC-info traits/registration and a separate unit-test fixture; the failing Windows x86 decoder and frame-scanning implementation are unchanged by it.
Known Workarounds
None established.
Configuration
Windows x86 runtime, Release, cDAC GC-reference stress,
NotYetLoadedArgTypedebuggee. The Helix host queue is Windows x64.Other information
This issue deliberately matches only the missing prestub-frame root, not every stress-test failure. Root cause is still open; the log indicates an interior reference (
Flags=0x1).Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1620305
Build error leg or test failing: windows-x86 release CdacStressTest - Microsoft.Diagnostics.DataContractReader.Tests.GCStress.CdacStressTests.GCRefStress_AllVerificationsPass
Pull request: #135055
Failure log: https://helix.dot.net/api/2019-06-17/jobs/eb8ed009-397d-4232-80ff-636980b1e497/workitems/CdacStressTests/console
KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.Error Message.ErrorPatternuses .NETSingleline | IgnoreCase | NonBacktrackingmatching with a 50ms-per-line timeout.[^\n]*instead of.*, and avoid catastrophic backtracking.BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.Error Details
The debuggee's other two failed verifications have the separately tracked EventSource root-count signature; this issue does not match those.
Error Message
{ "ErrorMessage": "", "ErrorPattern": "^\\s*Frame #0 <frame PrestubMethodFrame 0x[0-9a-f]+> \\[MISMATCH\\] cDAC=0 RT=1\\b", "BuildRetry": false, "ExcludeConsoleLog": false }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log
The anchored pattern was verified against the failing Helix console; no passing or skipped line matches. Only the volatile frame address is generalized.
Note
Prepared with GitHub Copilot.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1620305
Error message validated:
[^\s*Frame #0 <frame PrestubMethodFrame 0x[0-9a-f]+> \[MISMATCH\] cDAC=0 RT=1\b]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/2/2026 9:10:13 AM UTC
Report
Summary