After installing .NET 11.0 SDK, Running the 10.0 Blazor WebAssembly - memory access out of bounds

[jinzhao1127]

REGRESSION INFO: Works well on 11.0/9.0/8.0

INSTALL STEPS:

1. Clean Win11 x64 25h2 ENU

2. Install VS 18.4 Insiders 1

   • Web workload

3. Install the .NET 11.0 Preview 1 SDK: https://aka.ms/dotnet/11.0.1xx-preview1/daily/dotnet-sdk-win-x64.exe

4. Add feed

Platform

• Windows
• macOS
• Linux

Repro Steps

1. Open a normal Command Prompt
2. Create a blazor webAssembly project

   dotnet new blazor -int WebAssembly -o WASM -f net10.0
   

3. Open this project with VS
4. Ctrl + F5 to run the project

Actual Result
The project can't be load with error "Failed to start platform. Reason: RuntimeError: memory access out of bounds"

Note

1. This issue does not reproduce on dotnet run

2. This issue also reproduces on 10.0 Blazor Web (webassembly/Auto) app and wasm browser app with same error:

3. This issue also repro on 10.0 Blazor wasm Standalone project after installing 11.0 SDK
   

4. When F5 to run the project , will pop up an exception in VS:
   

   Error: Failed to start platform. Reason: RuntimeError: memory access out of bounds
   StackTrace:
    at qt (https://localhost:7118/_framework/blazor.webassembly.66stpp682q.js:1:58420)
   

5. The same issue #65034 but fixed on 11.0 Preview 1-26071.101

Error Log

dotnet.93hwfb1cdg.js:4  MONO_WASM: Failed to invoke 'onRuntimeReady' on library initializer '../_content/Microsoft.DotNet.HotReload.WebAssembly.Browser/Microsoft.DotNet.HotReload.WebAssembly.Browser.99zm1jdh75.lib.module.js': RuntimeError: memory access out of bounds
E @ dotnet.93hwfb1cdg.js:4
ye @ dotnet.93hwfb1cdg.js:4
await in ye
be @ dotnet.93hwfb1cdg.js:4
(anonymous) @ dotnet.93hwfb1cdg.js:4
await in (anonymous)
ct @ dotnet.93hwfb1cdg.js:4
await in ct
(anonymous) @ dotnet.93hwfb1cdg.js:4
create @ dotnet.93hwfb1cdg.js:4
(anonymous) @ blazor.web.2i0r6wwb69.js:1
await in (anonymous)
load @ blazor.web.2i0r6wwb69.js:1
(anonymous) @ blazor.web.2i0r6wwb69.js:1
await in (anonymous)
Kr @ blazor.web.2i0r6wwb69.js:1
startLoadingWebAssemblyIfNotStarted @ blazor.web.2i0r6wwb69.js:1
registerComponent @ blazor.web.2i0r6wwb69.js:1
li @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ii @ blazor.web.2i0r6wwb69.js:1
(anonymous) @ blazor.web.2i0r6wwb69.js:1
write @ blazor.web.2i0r6wwb69.js:1
dotnet.93hwfb1cdg.js:4  MONO_WASM: memory access out of bounds
RuntimeError: memory access out of bounds
    at dotnet.native.befq3iek54.wasm:0x10c971
    at dotnet.native.befq3iek54.wasm:0x6307c
    at dotnet.native.befq3iek54.wasm:0x62826
    at dotnet.native.befq3iek54.wasm:0x66e26
    at dotnet.native.befq3iek54.wasm:0x7315
    at dotnet.native.befq3iek54.wasm:0x1f774
    at dotnet.native.befq3iek54.wasm:0x1ca99
    at dotnet.native.befq3iek54.wasm:0xebe8
    at dotnet.native.befq3iek54.wasm:0x1d975
    at dotnet.native.befq3iek54.wasm:0xf17d1
_ @ dotnet.93hwfb1cdg.js:4
(anonymous) @ dotnet.93hwfb1cdg.js:4
Xe @ dotnet.93hwfb1cdg.js:4
ye @ dotnet.93hwfb1cdg.js:4
await in ye
be @ dotnet.93hwfb1cdg.js:4
(anonymous) @ dotnet.93hwfb1cdg.js:4
await in (anonymous)
ct @ dotnet.93hwfb1cdg.js:4
await in ct
(anonymous) @ dotnet.93hwfb1cdg.js:4
create @ dotnet.93hwfb1cdg.js:4
(anonymous) @ blazor.web.2i0r6wwb69.js:1
await in (anonymous)
load @ blazor.web.2i0r6wwb69.js:1
(anonymous) @ blazor.web.2i0r6wwb69.js:1
await in (anonymous)
Kr @ blazor.web.2i0r6wwb69.js:1
startLoadingWebAssemblyIfNotStarted @ blazor.web.2i0r6wwb69.js:1
registerComponent @ blazor.web.2i0r6wwb69.js:1
li @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ai @ blazor.web.2i0r6wwb69.js:1
si @ blazor.web.2i0r6wwb69.js:1
ii @ blazor.web.2i0r6wwb69.js:1
(anonymous) @ blazor.web.2i0r6wwb69.js:1
write @ blazor.web.2i0r6wwb69.js:1
blazor.web.2i0r6wwb69.js:1  Uncaught (in promise) Error: Failed to start platform. Reason: RuntimeError: memory access out of bounds
    at Vr (blazor.web.2i0r6wwb69.js:1:176136)
Vr @ blazor.web.2i0r6wwb69.js:1
await in Vr
Jr @ blazor.web.2i0r6wwb69.js:1
startWebAssemblyIfNotStarted @ blazor.web.2i0r6wwb69.js:1
resolveRendererIdForDescriptor @ blazor.web.2i0r6wwb69.js:1
determinePendingOperation @ blazor.web.2i0r6wwb69.js:1
refreshRootComponents @ blazor.web.2i0r6wwb69.js:1
(anonymous) @ blazor.web.2i0r6wwb69.js:1
blazor.web.2i0r6wwb69.js:1  Uncaught (in promise) RuntimeError: memory access out of bounds

[jinzhao1127]

@ilonatommy , Could you please take a look, this issue appears again.

[ilonatommy]

For .NET 10+ apps, the Microsoft.DotNet.HotReload.WebAssembly.Browser package is implicitly added:

https://github.com/dotnet/sdk/blame/bb7a82d677c1b8e9937c5d7e6ac1303ca00de0f7/src/WasmSdk/Sdk/Sdk.targets#L26

The package version is $(NETCoreSdkVersion) - which is the SDK version (11.0). So even when targeting .NET 10, the app gets the .NET 11 version of the HotReload package. The fix in dotnet/sdk#52517 was for a similar issue but in dotnet-watch startup hooks. We need similar pinning for Microsoft.DotNet.HotReload.WebAssembly.Browser.