[Problem/Bug]: Issue with msedgewebview2.exe Crashing from Version 133 Onwards. #5415
Description
What happened?
Hi,
We’ve been investigating a recurring issue and found that it appears to have been introduced starting from version 133. The msedgewebview2.exe works seamlessly with msedgedriver.exe up to version 132, but from version 133 onwards, it consistently crashes. We’ve tested up to version 141 and observed the same behavior.
Let me explain the scenario in more detail:
In our application, we embed React-based forms within the Edge browser using msedgewebview2. There are three such forms, and we use Selenium automation scripts (which internally rely on msedgedriver.exe) to perform workflows across these modules.
Here’s the sequence:
The automation script opens Form 1 and performs some operations.
Without closing Form 1, it opens Form 2 and continues with additional actions.
At this point, 2–3 instances of msedgedriver.exe may be visible in the Task Manager.
When the script attempts to open Form 3, msedgewebview2.exe crashes and all running instances are terminated.
Observation: If there are multiple instances (2–3) of msedgedriver.exe running, attempting to open another msedgewebview2-embedded browser—either manually or via automation—results in a crash.
This issue is significantly impacting our UI automation workflows. Could you please advise on when we can expect a fix or if there’s a known workaround?
Looking forward to your support.
This issue is also reproducible in WPF framework.
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
141.0.3537.71
SDK Version
No response
Framework
Win32
Operating System
Windows Server
OS Version
Windows server 2025, Windows 11
Repro steps
In our application, we embed React-based forms within the Edge browser using msedgewebview2. There are three such forms, and we use Selenium automation scripts (which internally rely on msedgedriver.exe) to perform workflows across these modules.
Here’s the sequence:
The automation script opens Form 1 and performs some operations.
Without closing Form 1, it opens Form 2 and continues with additional actions.
At this point, 2–3 instances of msedgedriver.exe may be visible in the Task Manager.
When the script attempts to open Form 3, msedgewebview2.exe crashes and all running instances are terminated.
Observation: If there are multiple instances (2–3) of msedgedriver.exe running, attempting to open another msedgewebview2-embedded browser—either manually or via automation—results in a crash.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
132.0.2957.140