Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Blazor WASM, Web App(Auto,WASM) Repeatedly Re-renders in Debug Mode When Using WebAssembly.instantiateStreaming via Web Worker #115300

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.

Sign up for GitHub

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

Jump to bottom
Open
1 task done
GokulprasathVenkatachalam opened this issue Apr 30, 2025 · 4 comments
Open
1 task done

Blazor WASM, Web App(Auto,WASM) Repeatedly Re-renders in Debug Mode When Using WebAssembly.instantiateStreaming via Web Worker #115300

GokulprasathVenkatachalam opened this issue Apr 30, 2025 · 4 comments
Assignees
@maraf
Labels
area-Debugger-mono
Milestone
Future

Comments

@GokulprasathVenkatachalam
Copy link

GokulprasathVenkatachalam commented Apr 30, 2025 •
edited
Loading

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

When running Visual Studio 2022 (v17.13.6) in administrator mode, loading a simple.wasm file in a Blazor WebAssembly application through a Web Worker using WebAssembly.instantiateStreaming results in the page continuously re-rendering when the application is executed in debug mode with a breakpoint set.

Expected Behavior

The application should pause at the breakpoint and continue executing as normal after resuming.

Steps To Reproduce

  • Open Visual Studio 2022 (v17.13.6) in administrator mode.

Image

  • Load a Blazor WebAssembly application that uses a Web Worker to instantiate a .wasm file via WebAssembly.instantiateStreaming.

  • Set a breakpoint in the Home.razor file code.

Image

  • Run the application in debug mode.

Exceptions (if any)

No response

.NET Version

9.0.203

Anything else?

Issue Video Reference: Continuously re-rendering.mp4

Sample: Sample.zip
@javiercn javiercn transferred this issue from dotnet/aspnetcore May 5, 2025
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label May 5, 2025
@dotnet-policy-service Dotnet Policy Service
Copy link
Contributor

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

@lewing
Copy link
Member

lewing commented May 5, 2025

Does this only happen in administrator mode?

@GokulprasathVenkatachalam
Copy link
Author

Hi @lewing,
Yes, the issue occurs only in administrator mode.

@lewing
Copy link
Member

lewing commented May 5, 2025

I suspect the underlying cause here is the browser enabling more protections when run as administrator which are failing to correctly load the runtime.

@lewing lewing removed the untriaged New issue has not been triaged by the area owner label May 5, 2025
@lewing lewing added this to the Future milestone May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maraf maraf

Labels
area-Debugger-mono
Projects
None yet
Milestone
Future
Development

No branches or pull requests
3 participants
@lewing @maraf @GokulprasathVenkatachalam