[Problem/Bug]: WebView2 keeps crashing, and restarting the client doesn't solve the problem

[zprettytext]

What happened?

We encountered an occasional serious WebView2 problem, the problem is as follows:
Background:
We embed webView2 in C++ Native client.

Problem: We encountered a case where the webView2 control can be created successfully after the Native client is started, but it continues to receive OnProcessFailed callbacks, and the crash type is: COREWEBVIEW2_PROCESS_FAILED_KIND_RENDER_PROCESS_UNRESPONSIVE

This problem has the following characteristics:

1. Restarting the Native client does not restore it, and it continues to receive OnProcessFailed callbacks.
2. Deleting the cache folder of WebView2, restarting the Native client does not restore it, and it continues to receive OnProcessFailed callbacks.
3. Restarting the computer can restore to normal.
4. This problem of WebVIew2 seems to have always existed, and we have always found such problems in the past.

Due to the lack of code details, it is difficult for us to locate the real cause of the problem.

In addition, we used the command line --enable-logging --v=1 --log-file=d:\webview2.log to open the webview2 log and collected normal logs and abnormal logs. The listed logs are as follows:
Normal log:
webview2.log
Abnormal log
webview2 - Copy.log

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

125.0.2535.92

SDK Version

1.0221

Framework

Win32

Operating System

Windows 11

OS Version

No response

Repro steps

1.start native client.
2.load webview2.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

[lflores-ms]

Hi @zprettytext, it's hard to tell from log why the renderer is becoming unresponsive. However, most of the time this event is produced by the web content running long scripts or the overall load on the system. See Handle unresponsive renderers. Have you observed this event on a particular URL?