-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 UI Freezes entirely on .NET 7 #12262
Comments
I have this happen when I horizontally scroll too fast/erratically (a degree a normal user would try to scroll). A very simple repro is to make a Maui Blazor app from the template, make an element that can horizontally scroll, and then scroll left and right quickly and erratically by dragging the scrollbar back and forth or hold Shift and use the scroll wheel to scroll up and down. You can consistently avoid the freeze by slowing scrolling using the arrows on the scrollbar. I don't know if speed is the cause, but it's the only correlation I can think of. |
@nathanjeynes thanks for contacting us. Does this happen on a regular webui without blazor? |
Hi @nathanjeynes. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time. |
Hi @javiercn yes this seems to be a problem with the built in MAUI WebView also. Thanks |
I can confirm that the example repository is freezing the UI. Hope someone can check it out and figure out whats going on; I'm really having a blast with MAUI and Blazor and would love to release my app using it :) |
This should be a priority 1 bug as its stopping customers progressing on production, there just seems to be zero urgency. |
Agree - we are unable to release our apps to customers as it happens so frequently, I hope this gets resolved soon. |
Is there any solution/workaround/progress on this? it's erratic but i could narrow it down to when the windows loses focus. it hangs. |
Only way to get around it is to downgrade the runtime to 6, but for some of us, that's not an option. I wouldn't expect this to be looked at any time soon, Its already been an issue since November and not a single member from the WebView team has replied. Its genuinely mind boggling... |
That's unfortunate, thanks for your reply. |
This appears to be an issue with WebView2. I'm able to reproduce with a WinUI3 app and WebView2. As reported the mouse stops working but keyboard inputs still seem to work. This appears to a known WebView2 issue tracked by MicrosoftEdge/WebView2Feedback#3003. Please comment and upvote as appropriate. |
Indeed, this is a duplicate of MicrosoftEdge/WebView2Feedback#3003. |
Description
I'm having an issue where the entire blazor UI freezes on Windows and does not accept any mouse clicks.
This specifically happens when holding a key on the keyboard for an excessive amount of time - and seems to happen regardless of the key. The time varies but usually happens after 10-15 seconds.
This has only happened since .NET 7 , and when targeting .NET 6 this is not a problem.
Unfortunately there are no console warnings or other logs that help point to the cause, but it is easy to replicate as below.
This is affecting all UI components from simple buttons to 3rd party components like the syncfusion datatable, and was picked up because a user was attempting to multi select rows in a data table by holding control key.
Steps to Reproduce
Expected outcome:
The UI does not freeze and continues to respond as in .NET 6
Actual outcome
The UI freezes causing the user to have to force quit and re-launch the app
Link to public reproduction project repository
https://github.com/nathanjeynes/ExampleUIFreezeBug
Version with bug
7.0 (current)
Last version that worked well
6.0 Release Candidate 2 or older
Affected platforms
Windows
Affected platform versions
10.0.19041.0
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: