MicrosoftEdge
[Problem/Bug]: Web pages load very slowly with the latest version of the webview2 runtime
What happened?
Web pages started taking a long time to load after updating to the webview2 runtime from version 120.0.221.61 to 120.0.2210.77 and 120.0.2210.89.
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
120.0.2210.89, 120.0.2210.77
SDK Version
1.0.1418.22 and 1.0.2210.55
Framework
Winforms
Operating System
Windows Server
OS Version
Windows Server 2019 Version 1809 Build 17763.5122
Repro steps
I can reproduce it on Windows Server 2019 only from my app and WebView2WindowsFormsBrowser demo app.
Repros in Edge Browser
No
Regression
Regression in newer Runtime
Last working version (if regression)
120.0.2210.61
I`ve updated win server 2019. Current build is 17763.5206, webview2 runtime is 120.0.2210.77 and the problem seems to be gone. Could this mean that not all versions of Windows Server 2019 are 100% compatible with certain versions of the webview2 runtime?
Could you please capture net log if it repro again following instructions at Capture Network Logs (NetLog) from Edge and Chrome (and Electron and WebView2) – text/plain (textslashplain.com)?
@LiangTheDev sorry for my delayed response.
I created Webview2WinformsTestApp and reproduced the issue using this app in Windows Server 2019. I started my virtual machine with webview2-runtime 123.0.2420.81 installed, after some time the runtime was automatically updated to 123.0.2420.97, after that Webview2 takes about 20 sec to initialize and page navigation also takes 20 sec.
Before update
After
I captured netlog before and after update. netlog_before_update.json netlog_after.json
The problem seems to reproduce only on Windows Server 2019. I have not been able to reproduce it on win 10-11.
Also, I found that this can be resolved by simply restarting the VM after updating the webview2 runtime, but the user cannot restart or shut down the VM in my case.
Is there any solution for this without restarting the VM or is it possible to configure the update only with the windows update?
The netlog doesn't provide any clues. As WebView2 initialization also becomes slow, it seems that something else is going on. Could you please capture an ETW trace (https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/diagnostics/etw.md) and share via some cloud drive to [email protected]?