-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Open
Labels
area-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Components
Description
REGRESSION INFO: Works well on 10.0 RC 1 and Previous 10.0 RC 2 build
INSTALL STEPS:
- Install Latest 10.0 RC 2 from Release Tracker
- Apply Feed and do feed workaround
Platform
- Windows
- macOS
- Linux
Repro Steps
- Open up a normal Command Prompt (Terminal)
- Create a Blazor Web App for WebAssembly
dotnet new blazor -int WebAssembly -o wasm cd wasm/wasm
- Publish the project with
dotnet publish
- Go to the publish folder and run
dotnet wasm.dll
. - Open the browser and go to the
http://localhost:5000/counter
- Open the browser developer console window
Actual Result
There is no any response and the console window contains some error

Error Log
dotnet.runtime.fn94ls2wwa.js:3
[MONO] * Assertion at /__w/1/s/src/runtime/src/mono/mono/metadata/assembly.c:2718, condition `<disabled>' not met
Error
at Mc (dotnet.runtime.fn94ls2wwa.js:3:172298)
at dotnet.native.ggch313emy.wasm:0xac62
at dotnet.native.ggch313emy.wasm:0x43c51
at dotnet.native.ggch313emy.wasm:0x42301
at dotnet.native.ggch313emy.wasm:0x42422
at dotnet.native.ggch313emy.wasm:0x42465
at dotnet.native.ggch313emy.wasm:0x42438
at dotnet.native.ggch313emy.wasm:0x8cd9
at Module._mono_wasm_load_runtime [as mono_wasm_load_runtime] (dotnet.native.98v1chuo8c.js:8:113231)
at dotnet.runtime.fn94ls2wwa.js:3:188734
dotnet.runtime.fn94ls2wwa.js:3
MONO_WASM: mono_wasm_load_runtime () failed [object Object]
[NEW] Explain Console errors by using Copilot in Edge: click
to explain an error. Learn more
Don't show again
dotnet.runtime.fn94ls2wwa.js:3
Uncaught (in promise)
ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1, silent: true}
dotnet.runtime.fn94ls2wwa.js:3
Uncaught (in promise)
ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1, silent: true}
blazor.web.911ktl676v.js:1
Uncaught (in promise) Error: Failed to start platform. Reason: [object Object]
at Vr (blazor.web.911ktl676v.js:1:176030)
blazor.web.911ktl676v.js:1
Uncaught (in promise)
ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1, silent: true}
Expected Result:
There is no any error when click counter button
Note:
- This issue does not repro on Blazor Web Server app
- This issue does not repro when
dotnet run
- This issue does not reproduce on the previous build
- This issue also reproduces on 9.0 project after installing 10.0 RC 2
Metadata
Metadata
Assignees
Labels
area-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Components