[Problem/Bug]: ICoreWebView2CreateCoreWebView2ControllerCompletedHandler comes back with RCP_E_DISCONNECTED after a 15 hour idle period

What happened?

We have a Windows Desktop App running on Windows 10. We use WebView2 objects to display some UI items. We typically have one WebView2 alive all the time (without showing the UI to the user). And when needed, we show other WebViews (all sharing the same user data folder). This works well most of the time. However, if we leave the machine idle for more than 15 hours (no sleep / power state change, our app is still running, and active), the next time we try to create a WebView, we get this error in the CotnrollerCompletedHandler.

Once this happens - all further attempts to create the controller fail in the same way. The sync. part works, but the callback comes back with this error.

The edge processes are all running (no crashes), there is no version update, etc.

If we kill the associated browser process manually - everything goes back to normal.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

151.0.4129.78

SDK Version

No response

Framework

Win32

Operating System

Windows 10

OS Version

10.0.17763 Build 17763

Repro steps

1. Create a WebView2 component embedded in a Window - no need to show the window.
2. Create a second WebView2 component, new environment, but using the same data folder as the first one.
3. Destroy the second component.
4. Wait for about 15 hours.
5. Again create a WebView2 component - same as step 2 above.

Expected Result: The new component will function correctly.
Actual Result: ICoreWebView2CreateCoreWebView2ControllerCompletedHandler comes back with errorCode = RPC_E_DISCONNECTED

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Start with the listed repro steps and the ICoreWebView2CreateCoreWebView2ControllerCompletedHandler callback, focusing on the shared user data folder and the browser process after the 15-hour idle period. Compare the failing controller creation with the manual browser-process restart described in the report. Done means identifying a reproducible cause or a documented fix for RPC_E_DISCONNECTED on the stated Windows and WebView2 versions.