What happened?
Following a recent WebView2 runtime update, we are observing significant system-wide memory leaks and performance degradation over time during WPF/WebView2 frame rendering.
The issue appears to be an event leak related to NVIDIA filters and ETW/ETS buffers rather than application-level code. Closing the application does not release the leaked memory; however, restarting the application sometimes resets the accumulated event count.
The leaked memory is not bound to a specific process ID because it populates via system events. It likely stems from aggressive tracing being accidentally triggered on the thread. This started occurring globally across installations immediately following a recent WebView2 runtime update.
The memory bias can be forced to clear out by killing the NVIDIA filters via the command line:
logman stop "NVIDIA-NVTOPPS-FILTER" -ets
logman stop "NVIDIA-NVTOPPS-NOCAT" -ets
We are currently working with our users to collect deeper trace logs (.etl). Because this issue is tied directly to the latest WebView2 runtime behavior and its interaction with NVIDIA's telemetry pipeline, we will likely need upstream input/collaboration from Microsoft and NVIDIA to isolate the exact trace registration registration bug.
You can find our associated tracking issue here: ciderapp/Cider-2#1370
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
145.0.3800.82, and latest as of this issue, 149.0.4022.8
SDK Version
1.0.3351.48 (This also occurs on the latest SDK version)
Framework
WPF
Operating System
Windows 11
OS Version
26220.8474
Repro steps
Currently unknown circumstance, although it seems to commonly invoke on the latest NVIDIA driver combined with a subsequent system sleep and wake with the WebView2 application open in the background.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
1.0.3351.48, 143.0.3650.139
What happened?
Following a recent WebView2 runtime update, we are observing significant system-wide memory leaks and performance degradation over time during WPF/WebView2 frame rendering.
The issue appears to be an event leak related to NVIDIA filters and ETW/ETS buffers rather than application-level code. Closing the application does not release the leaked memory; however, restarting the application sometimes resets the accumulated event count.
The leaked memory is not bound to a specific process ID because it populates via system events. It likely stems from aggressive tracing being accidentally triggered on the thread. This started occurring globally across installations immediately following a recent WebView2 runtime update.
The memory bias can be forced to clear out by killing the NVIDIA filters via the command line:
We are currently working with our users to collect deeper trace logs (.etl). Because this issue is tied directly to the latest WebView2 runtime behavior and its interaction with NVIDIA's telemetry pipeline, we will likely need upstream input/collaboration from Microsoft and NVIDIA to isolate the exact trace registration registration bug.
You can find our associated tracking issue here: ciderapp/Cider-2#1370
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
145.0.3800.82, and latest as of this issue, 149.0.4022.8
SDK Version
1.0.3351.48 (This also occurs on the latest SDK version)
Framework
WPF
Operating System
Windows 11
OS Version
26220.8474
Repro steps
Currently unknown circumstance, although it seems to commonly invoke on the latest NVIDIA driver combined with a subsequent system sleep and wake with the WebView2 application open in the background.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
1.0.3351.48, 143.0.3650.139