MAUI Webview Process Lifecycle/Crash events

[prerakpatel2]

Description

Expose the lifecycle events of browsers through the API. As the Webviews run in separate processes, it is possible that they can crash or be forced to close by the user/OS. We should be able to react to those events so the app can recover the view if the webview processes crash. The lifecycle events would also allow us to hide the loading of the view until the process is ready for rendering.

Public API Changes

Webview view = new();
view.OnViewProcessTerminated += (event) => {
// Logic to stop processing data for the view and reinitialize the view, log error, or notify of successful shutdown
}
view.OnViewProcessReady += (event) => { logic to hide loading screen }
view.OnViewProcessCloseInitiated += (event) => { logic to cleanup view  }
}

Intended Use-Case

Recovering from crashed processes. We should be able to seamlessly recover from the crash, reload the view, and continue from where we left off. This would also enable to preload the webview and know its ready for rendering when opening a webview based tool.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[Redth]

We should ensure that the various delegates for WKWebView can be easily passed in as custom instances.

We do this for UIDelegate currently in a mapper. Navigation Delegate would need the same treatment.

Related to #7551

[mgungorchamp]

This crashed my app - and I cannot do anything about it. Is there a away to prevent this crash?

[chromium] [INFO:CONSOLE(0)] "Access to XMLHttpRequest at 'https://api.rlcdn.com/api/identity/envelope?pid=1258' from origin 'https://weather.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.", source: about:srcdoc (0)
[cr_ChildProcessConn] onServiceDisconnected (crash or killed by oom): pid=10174 bindings:W S
[chromium] [ERROR:aw_browser_terminator.cc(156)] Renderer process (10174) crash detected (code 5).
[chromium] [FATAL:crashpad_client_linux.cc(732)] Render process (10174)'s crash wasn't handled by all associated webviews, triggering application crash.
[libc] Fatal signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0xcc9e58be in tid 10036 (board.infoboard), pid 10036 (board.infoboard)

[Eilon]

BTW here was a sample of how the process terminated event can be used specifically for BlazorWebView scenarios (not regular WebView): #6481 (comment)

[rmarinho]

Fixed by #20059