[Problem/Bug]: Crash in WebView2 Composition Controller initialization on Windows 11 (Build 26100) with Intel Iris Xe (WDDM 3.2) #5479
Description
What happened?
We are encountering a native process crash (Access Violation in MSVCP140.dll) when initializing WebView2 in Composition Controller mode on a subset of Windows devices.
This issue does not occur on most machines, but consistently reproduces on certain configurations.
The crash happens before any WebView callbacks or application-level error handling, making it impossible to catch or recover in user code.
Environment (Affected Devices)
OS: Windows 11, Build 26100
GPU: Intel Iris Xe Graphics (integrated, UMA)
CPU: 13th Gen Intel Core (e.g. i7-1360P)
GPU Driver: Intel driver, WDDM 3.2
WebView2 Runtime: Installed (Evergreen, latest at time of testing)
WebView Mode: Composition Controller
App Framework: Flutter Windows (D3D-based rendering)
Symptoms
Application crashes immediately during WebView2 initialization.
No WebView2 error callback is invoked.
No HRESULT error is returned.
Crash occurs in native code, typically reported as:
MSVCP140.dll
std::mutex::lock
GPU-related paths (e.g. TextureBridgeGpu in dumps)
Reinstalling WebView2 Runtime does not resolve the issue.
What We Observed
The issue only occurs when using Composition Controller (GPU texture-based integration).
On unaffected devices, WebView2 either initializes normally or fails gracefully with an error.
On affected devices, initialization leads to use-after-free / race-condition-like behavior between GPU threads.
This suggests a GPU resource lifecycle synchronization issue between:
WebView2 Composition surfaces
Host application GPU rendering threads
Specific GPU driver + OS combinations
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
Other
Operating System
Windows 11
OS Version
26100
Repro steps
Approximately 7–8% of real-world customer devices are affected.
This is not an isolated edge case.
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