What happened?

A recent update to the WebView2 runtime is causing a WebView2 session in my app to become inoperable at a specific stage of being in use. This takes place when my WinUI 3 app opens a WebView2 session (for my web app). I first noticed this with runtime version 124.0.2478.67, but it could be possible that the regression was first introduced with runtime version 124.0.2478.51. This is not reproduceable in the Edge app, only the runtime. The following video demonstrates the regression, causing a freeze in my web app for 15 seconds:

The next time I open the app and try again, the same freeze has a duration of only two seconds. The following video demonstrates the same process with no freezing, as per runtime version 123.0.2420.65:

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

124.0.2478.67

SDK Version

1.0.2210.55

Framework

WinUI3/WinAppSDK

Operating System

Windows 10, Windows 11

OS Version

22631.3447

Repro steps

(Please see videos.)

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

123.0.2420.65

AB#51402837