Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor WebAssembly: "An unhandled error has occurred. Reload" since .NET 8.0.5 #102307

Closed
ghost opened this issue May 16, 2024 · 4 comments
Closed
Assignees
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono os-browser Browser variant of arch-wasm
Milestone

Comments

@ghost
Copy link

ghost commented May 16, 2024

Description

Since the update of Visual Studio to version 17.9.7 and .NET 8.0.5, an error is produced when starting Blazor Webassembly applications in release mode in the Edge Browser from Visual Studio ("An unhandled error has occurred. Reload").
This error occurs with all Blazor Webassembly applications.
To reproduce it, I created a completely new and empty Blazor Webassembly app. The error occurs even without any changes.

blazor_error

An example project can be found here:
https://github.com/Coding-Victim/BlazorApp1

Reproduction Steps

Create an empty Blazor WebAssembly project, select "Release", start the project with the MS Edge browser (newest Version)

Expected behavior

The empty WebAssembly app starts without any problems

Actual behavior

The empty WebAssembly app starts, but the MS Edge shows the message: "An unhandled error has occurred. Reload"

In the HTML, style="display: block;" is automatically added to the line

. This actually only happens if an exception is thrown. Since .NET 8.0.5, this already happens when the empty project is started through Visual Studio with MS Edge browser.

Regression?

In .NET 8.0.4 it worked in all projects without any problems

Known Workarounds

No response

Configuration

.NET 8.0.5
Visual Studio 2022 (v17.9.7)
Windows 10 and 11
MS Edge

Other information

No response

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label May 16, 2024
@maraf
Copy link
Member

maraf commented May 17, 2024

It looks like a duplicate of #102272. Please see devtools console for error details. Let us know if the issue is different

@maraf maraf added needs-author-action An issue or pull request that requires more info or actions from the author. arch-wasm WebAssembly architecture area-Build-mono os-browser Browser variant of arch-wasm and removed area-Debugger-mono labels May 17, 2024
@ghost
Copy link
Author

ghost commented May 17, 2024

I think the issue is different. I got the following error in the browser console.

blazor.webassembly.js:1  DEBUGGING IS NOT ENABLED
Dt @ blazor.webassembly.js:1
put_char @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
write @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
write @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
doWritev @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
_fd_write @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
$func8373 @ 00b2193a:0x1fb5df
$func8387 @ 00b2193a:0x1fbd0d
$func8388 @ 00b2193a:0x1fbdb6
$func8382 @ 00b2193a:0x1fbc0e
$func549 @ 00b2193a:0x3bd8c
$func548 @ 00b2193a:0x3bd6d
$mono_wasm_send_dbg_command @ 00b2193a:0x6dcf8
Module._mono_wasm_send_dbg_command @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
e.<computed> @ cwraps.ts:338
Bt @ debug.ts:89
(anonym) @ VM14:1
mono_wasm_runtime_ready @ debug.ts:32
(anonym) @ startup.ts:290
await in (anonym) (asynchron)
Nl.e.onRuntimeInitialized @ startup.ts:92
doRun @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
run @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
runCaller @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
removeRunDependency @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
(anonym) @ startup.ts:232
await in (anonym) (asynchron)
Nl.e.preRun @ startup.ts:90
callRuntimeCallbacks @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
preRun @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
run @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
runCaller @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
removeRunDependency @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
(anonym) @ startup.ts:505
await in (anonym) (asynchron)
(anonym) @ startup.ts:138
Nl.e.instantiateWasm @ startup.ts:86
createWasm @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
(anonym) @ dotnet.native.8.0.5.p7qv7rl7e4.js:8
Fe @ run.ts:464
await in Fe (asynchron)
(anonym) @ run.ts:505
await in (anonym) (asynchron)
Pe @ run.ts:428
await in Pe (asynchron)
create @ run.ts:362
(anonym) @ blazor.webassembly.js:1
await in (anonym) (asynchron)
load @ blazor.webassembly.js:1
(anonym) @ blazor.webassembly.js:1
await in (anonym) (asynchron)
hn @ blazor.webassembly.js:1
mn @ blazor.webassembly.js:1
fn @ blazor.webassembly.js:1
An @ blazor.webassembly.js:1
(anonym) @ blazor.webassembly.js:1
(anonym) @ blazor.webassembly.js:1

@dotnet-policy-service dotnet-policy-service bot removed the needs-author-action An issue or pull request that requires more info or actions from the author. label May 17, 2024
@maraf
Copy link
Member

maraf commented May 21, 2024

cc @thaystg

Copy link
Contributor

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

@thaystg thaystg removed area-Debugger-mono untriaged New issue has not been triaged by the area owner labels May 22, 2024
@lewing lewing added this to the 9.0.0 milestone Jul 15, 2024
@maraf maraf closed this as completed Jul 26, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-VM-meta-mono os-browser Browser variant of arch-wasm
Projects
None yet
Development

No branches or pull requests

4 participants