[wasm][R2R] github60486 stack trace contains duplicate frames

[lewing]

Description

Loader/classloader/DefaultInterfaceMethods/regressions/github60486 observes duplicate stack frames in browser-wasm CoreCLR ReadyToRun execution.

Reproduction Steps

Run the default runtime pipeline for #133463 at commit 452dea3aba16d97244508b8a0fef4643de8dd26e (Azure DevOps build 1589007, test run 43860850).

Expected behavior

The test observes the expected default-interface-method stack frame sequence.

Actual behavior

Expected System.String[].TestMethod1 but got at System.Environment.get_StackTrace()
   at System.Environment.get_StackTrace()
   at System.Environment.get_StackTrace()
   at TestItf1`1.TestMethod1(...)
   at Program.Start()
   at Program.Start()
   at __GeneratedMainWrapper.Main()
   at __GeneratedMainWrapper.Main()

Regression?

Unknown; exposed by the restored browser-wasm R2R lane.

Known Workarounds

Skip only this test for wasm ReadyToRun.

Configuration

• CoreCLR browser-wasm
• Checked runtime
• ReadyToRun / crossgen2

Other information

Umbrella tracking: #133305.

Note

This issue was authored with GitHub Copilot.

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/crossgen-contrib
See info in area-owners.md if you want to be subscribed.