CoreWebView2.ProcessFailed Event

Definition

Namespace:

Microsoft.Web.WebView2.Core

Assembly:

Microsoft.Web.WebView2.Core.dll

Package:

Microsoft.Web.WebView2 v1.0.2849.39

ProcessFailed is raised when any of the processes in the WebView2 Process Group encounters one of the following conditions:

Condition	Details
Unexpected exit	The process indicated by the event args has exited unexpectedly (usually due to a crash). The failure might or might not be recoverable and some failures are auto-recoverable.
Unresponsiveness	The process indicated by the event args has become unresponsive to user input. This is only reported for renderer processes, and will run every few seconds until the process becomes responsive again.

Note: When the failing process is the browser process, a BrowserProcessExited event will run too.

Your application can use CoreWebView2ProcessFailedEventArgs to identify which condition and process the event is for, and to collect diagnostics and handle recovery if necessary. For more details about which cases need to be handled by your application, see CoreWebView2ProcessFailedKind.

public event EventHandler<Microsoft.Web.WebView2.Core.CoreWebView2ProcessFailedEventArgs> ProcessFailed;

member this.ProcessFailed : EventHandler<Microsoft.Web.WebView2.Core.CoreWebView2ProcessFailedEventArgs> 

Public Custom Event ProcessFailed As EventHandler(Of CoreWebView2ProcessFailedEventArgs) 

Event Type

EventHandler<CoreWebView2ProcessFailedEventArgs>

Examples

webView.CoreWebView2.ProcessFailed += WebView_ProcessFailed;

Remarks

ProcessFailed is raised when any of the processes in the WebView2 Process Group encounters one of the following conditions:

Condition	Details
Unexpected exit	The process indicated by the event args has exited unexpectedly (usually due to a crash). The failure might or might not be recoverable, and some failures are auto-recoverable.
Unresponsiveness	The process indicated by the event args has become unresponsive to user input. This is only reported for renderer processes, and will run every few seconds until the process becomes responsive again.

Note: When the failing process is the browser process, a BrowserProcessExited event will run too.

Your application can use CoreWebView2ProcessFailedEventArgs to identify which condition and process the event is for, and to collect diagnostics and handle recovery if necessary. For more details about which cases need to be handled by your application, see CoreWebView2ProcessFailedKind.