[Problem/Bug]: WebView2 browser process crash repeatedly for versions 136.0.3222.0 and above

[pontusn]

What happened?

After automatic upgrade our embedded WebView2 started crashing. Crash occurs after initial navigation but before any interaction.

Importance

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

Runtime Channel

Prerelease (Edge Canary/Dev/Beta)

Runtime Version

136.0.3223.0

SDK Version

Current and previous

Framework

Win32

Operating System

Windows 11

OS Version

24H2 (26100.3025)

Repro steps

Show embedded UI and programmatically load initial page.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

136.0.3216.0

[github-actions]

Hi, @pontusn!

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.

Thank you for your cooperation!

[pontusn]

4b5c40e5-7329-4f03-a1ca-7af93d564b12.dmp

[pontusn]

Please contact me if additional details are required.

Problem have been seen both in developer setups, but also for end-users running pre-release versions of WebView2. Crashing frequency seems worse in our login-dialog, but also affects general usage.

[SkipperRobbins]

My organization is seeing this as well with canary 136.0.3227.0. CoreWebView2ProcessFailedKind.BrowserProcessExited after initial navigation.

fa727134-5516-432d-bd75-1f37f8c32778.dmp

[ambikakunnath]

Thanks for reporting the issue. This issue is being worked upon. Will update once a build with fix is available.

[pontusn]

Updated:
We did not experience any crashed for current Canary.

[pushkin-]

same here

[ambikakunnath]

Thanks for the update. This issue is fixed in latest Canary.