[wasm][R2R] badcodeinsidefinally returns null instead of pass

[lewing]

Description

The debug and release badcodeinsidefinally Methodical tests fail in browser-wasm CoreCLR ReadyToRun execution because GetObj() returns null instead of the expected "pass" string.

Reproduction Steps

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

Expected behavior

GetObj() leaves the protected region with the local containing "pass"; both variants pass output verification.

Actual behavior

Both tests fail with:

Object reference not set to an instance of an object.
   at Test_badcodeinsidefinally.GetObj()
   at Test_badcodeinsidefinally.Main()

Regression?

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

Known Workarounds

Skip only the affected test type for wasm ReadyToRun, preserving normal wasm and non-wasm coverage.

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.

[AndyAyersMS]

Seems like a VM issue with collided exceptions.