You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has started happening for the past few days, so after the WebView2 120.0.2210.121, .Net Framework 4.8 update.
If you try to navigate to linkedin.com, facebook.com, or twitter.com the corewebview2 instance crashes and you see an empty panel where the webview2 was.
Other websites I have tested like google, bing, work fine. Seems to be limited to social media websites listed. Although instagram.com loads fine.
It seems that your issue contains the word "crash". If you have not already, could you attach a crash dump as a comment?
WV2 crash dumps are located in a subfolder of the app's user data folder (UDF): <UDF>\EBWebView\Crashpad\reports\. By default, the user data folder is created in the app's folder with a name like <App Exe Name>.exe.WebView2. Refer to Crash Diagnostics for more information.
What happened?
This has started happening for the past few days, so after the WebView2 120.0.2210.121, .Net Framework 4.8 update.
If you try to navigate to linkedin.com, facebook.com, or twitter.com the corewebview2 instance crashes and you see an empty panel where the webview2 was.
Other websites I have tested like google, bing, work fine. Seems to be limited to social media websites listed. Although instagram.com loads fine.
Another user has reported this here: https://stackoverflow.com/questions/77788574/webview2-latest-update-to-v-120-0-2210-121-opening-the-linkedin-com-crashes
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
120.0.2210.121
SDK Version
No response
Framework
WinUI2/UWP
Operating System
Windows 11
OS Version
No response
Repro steps
Add a webview2 control and set the source to linkedin.com, facebook.com, or twitter.com.
Repros in Edge Browser
No
Regression
Regression in newer Runtime
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: