[Problem/Bug]: The UI of an application sporadically appears to be frozen after opening WebView2 control

[AlexanderSchulz-Siemens]

What happened?

The behavior of the issue is described in the following existing issues:

• [Problem/Bug]: The UI of an application appears to be frozen when user changes system Scaling #5247
• [Problem/Bug]: Application freeze after DPI change #4485 (comment)

Unfortunately the behavior described in previously mentioned issue seems to happen also highly sporadically in situations where the user doesn't change the scaling but just opens a webview in our enterprise application. We had couple of people in the organization who ran into such kind of situation sporadically, without doing any scaling change on their machine before.

There was one colleague who had a new machine and run into this issue quite frequently. Unfortunately at this time we didn't have the memory dump creation knowledge which is mentioned in this 4485 comment 1. On his machine we could try out the PerMonitorV2 setting which is mentioned as a workaround here: 4485 comment 2 and it seemed to solve running in that behavior sporadically, but because of the reasons mentioned in the bug , this is not a feasible solution for our application.

Given that this behavior is sporadic and difficult to reproduce, our objective is to identify its potential root cause and verify whether the proposed solution for the associated bug also addresses these intermittent issues.

Meanwhile we informed all of our colleagues in the organization and raised the attention of this behavior and we will try to provide memory dumps in the future if someone runs into this situation again.

We have created memory dumps from the application and the WebView2 processes and can provide them directly to our Microsoft contacts.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

Latest

SDK Version

1.0.1518.46

Framework

Winforms

Operating System

Windows 11

OS Version

22631.5039

Repro steps

As of now, repro steps are unknown but internally we have been able to reproduce it if the application is open for 24 - 48 hours.

1. Connected to the test machine remote desktop
2. 20 minutes later, start the application
3. Open an editor which uses WebView2 WinForms control
4. Disconnected from the remote machine and leave the application open (machine was just locked)
5. Reconnect after 43 hours via RDP (reconnect from same machine, using same scaling, monitor, ...)
6. Access the application and open an additional editor which uses WebView2 Winforms control
7. Application goes into buggy state

Hint: With these steps the bug was not reproducible if the application is configured with PerMonitorV2 instead of SystemAware

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response