Web socket Exception crashing Blazor WASM while debugging in VS2022?

Alex Morris 1

I'm having some trouble trying to get Blazor WASM debugging to work with VS2022 17.3.3 and was wondering if anyone on here could give me a hand/ had encountered this issue before?

When running any Blazor WASM project(I've tried with a fresh project as well) with the debugger, it will open correctly and run for about ~10-60s, before crashing and closing the browser. I get the following error in the debug console:

https://i.stack.imgur.com/IREbQ.png

When running without debugger or via CLI the application runs without crashing.

I originally had an error in the browser identical to the one described here: https://learn.microsoft.com/en-us/answers/questions/741393/error-with-websocket.html but after disabling Hot Reload and Browser link this no longer started appearing, the crashing error still occurred though. Interestingly after re-enabling these settings the browser error has not reoccurred, and from what I can see hot reload isn't working at all when running with the debugger attatched.

Thanks for the help and happy to post any further details on my setup if anything else could be useful.

Zhi Lv - MSFT 32,006 Reputation points Microsoft Vendor

2022-10-03T02:26:54.507+00:00

Hi @Alex Morris ,

I get the following error in the debug console:

Console output of debug run

So, the error message is "Console output of debug run"?

You can try to restart the machine and then reopen the VS 2022 to test the application, whether it still crash or not?

Besides, try to upgrade the VS 2022 to the latest version (Microsoft Visual Studio Community 2022 Version 17.3.5), I have created a Blazor WASM application, there is no WebSocket connection error and the works well on debug mode.

Best regards,
Dillion
Alex Morris 1 Reputation point

2022-10-03T08:26:44.18+00:00

Copied this over from my duplicate stack overflow post in a rush, of course the hyperlink didn't copy over.... edited now to fix :))
Zhi Lv - MSFT 32,006 Reputation points Microsoft Vendor

2022-10-04T06:35:40.113+00:00

Hi @Alex Morris ,
I found some same question on Github (such as: this thread and this one), it seems that this issue has been fixed. So, I suggest you could try to update the VS 2022 to the latest version and create a new Blazor application to test it. If still meet the same error, can you create a minimal, complete sample to reproduce the problem, so that we can test it and narrow down the problem.

Best regards,
Dillion