[wasi][coreclr] Out of bounds memory access in the interpreter running AsyncProfilerTests

[lewing]

Description

System.Threading.Tasks.Tests crashes on CoreCLR WASI (trimmed ReadyToRun) with wasm trap: out of bounds memory access in the interpreter while running the async profiler tests. The last managed frame is System.Threading.Tasks.Tests.AsyncProfilerTests.StateMachineAsync_ValueTask_SingleThread_ChainEventsAndCallstack():

wasm trap: out of bounds memory access
    0: corerun!InterpExecMethod(InterpreterFrame*, InterpMethodContextFrame*, InterpThreadContext*, ExceptionClauseArgs*)
    1: corerun!ExecuteInterpretedMethod
    2: corerun!ExecuteInterpretedMethodWithArgs_PortableEntryPoint(unsigned long, TransitionBlock*, unsigned long, signed char*)
    3: corerun!WasmR2RToInterpreterThunk(iiaiip)

The crash takes down the whole suite, so no other results from it are reported. Reproduce the single test with the interpreter and with ReadyToRun to see whether the bad access comes from the R2R-to-interpreter transition or from the interpreter itself.

Seen in CoreCLR WASI library test runs for #134813; the non-R2R CI lane fails the same suite.

Note

This issue was drafted with the help of 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: @JulieLeeMSFT, @BrzVlad, @janvorli
See info in area-owners.md if you want to be subscribed.