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
Hello!
We've had used webview2 for a year aprox, but recently it's crashing (don't know why) and new webView2 instances created after crashing appears like white window with no content. If restarts the app it works again.
I'll update the report when whe get any info about this.
I've read about ProcessFailed event for listen for the crashes, we're including this in every use of webView2 in the app for gathering info about the issue.
Crash dumps on \EBWebView\crashpad\reports folder and folder of the app are empty.
I've read about it's possible to recreate the WebView2 without restarting the whole app, but I haven't find 'instructions' about this.
What I need is recreate the WebView2 without restarting the whole app, if possible, but I don't know how to make it.
Thanks!
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
Winforms
Operating System
Windows 10, Windows 11
OS Version
No response
Repro steps
Doesn't have
Repros in Edge Browser
No
Regression
Don't know
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered:
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.
There is known issue in 120.0.2210.121 which is fixed in Canary - you can try it if it will fix yours. Otherwise we need more info - dumps, error codes etc to make it actionable.
b508ce89-2ecc-4a3c-89a9-01d808efac74.dmp
I've attach a dump about the 'Facebook case'. But I've confimed about that's not our case of use because is not browsed.
WebView2 cannot create more instances and there isn't content on \EBWebView\Crashpad\reports.
However, I just tested on a client that could not create any more instances and ending the 'msedgewebview2.exe' processes associated with the application allowed me to create new instances without closing the application and reopening it.
What happened?
Hello!
We've had used webview2 for a year aprox, but recently it's crashing (don't know why) and new webView2 instances created after crashing appears like white window with no content. If restarts the app it works again.
I'll update the report when whe get any info about this.
I've read about ProcessFailed event for listen for the crashes, we're including this in every use of webView2 in the app for gathering info about the issue.
Crash dumps on \EBWebView\crashpad\reports folder and folder of the app are empty.
I've read about it's possible to recreate the WebView2 without restarting the whole app, but I haven't find 'instructions' about this.
What I need is recreate the WebView2 without restarting the whole app, if possible, but I don't know how to make it.
Thanks!
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
Winforms
Operating System
Windows 10, Windows 11
OS Version
No response
Repro steps
Doesn't have
Repros in Edge Browser
No
Regression
Don't know
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: