Open
Description
Repro steps:
- Install .NET 10 Preview 4 with wasm-tools workload
- Create new Blazor Web App with interactive WebAssembly rendering enabled
- Add MSBuild properties to the Client project to enable browser perf profiling:
<WasmProfilers>browser</WasmProfilers>
<WasmNativeStrip>false</WasmNativeStrip>
<WasmNativeDebugSymbols>true</WasmNativeDebugSymbols>
- Run the app and browse to the counter page
- In the browser dev tools performance tab, start a recording
- Click the counter a bunch of times and stop the recording
- Check the browser dev console:
dotnet.native.p6c5fv8ns5.wasm:0x294bd1 Uncaught (in promise) RuntimeError: memory access out of bounds
at dotnet.native.wasm.strlen (dotnet.native.p6c5fv8ns5.wasm:0x294bd1)
at dotnet.native.wasm.mono_wasm_method_get_name_ex (dotnet.native.p6c5fv8ns5.wasm:0x2b71df)
at Pc (profiler.ts:109:30)
at dotnet.native.wasm.method_leave (dotnet.native.p6c5fv8ns5.wasm:0x90b0)
at dotnet.native.wasm.mono_profiler_raise_method_leave (dotnet.native.p6c5fv8ns5.wasm:0xfbd2c)
at dotnet.native.wasm.mono_interp_profiler_raise (dotnet.native.p6c5fv8ns5.wasm:0x1b5d9)
at dotnet.native.wasm.mono_interp_exec_method (dotnet.native.p6c5fv8ns5.wasm:0x18290)
at dotnet.native.wasm.interp_runtime_invoke (dotnet.native.p6c5fv8ns5.wasm:0x1c36f)
at dotnet.native.wasm.mono_jit_runtime_invoke (dotnet.native.p6c5fv8ns5.wasm:0x1331a4)
at dotnet.native.wasm.do_runtime_invoke (dotnet.native.p6c5fv8ns5.wasm:0xf2238)