MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Memory leak on WebResourceResponseReceived event listener

Open
#5,138 3 comments 0 reactions 1 assignee View on GitHub

@prija-microsoft is already working on this.

Since Mar 7, 2025.

bug tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

I can see memory usage of the webview renderer processes steadily go up throughout the day when I use this event listener. I need to use this event listener in order to get the content of HTTP requests made by my webapps.

Even setting up an empty event listener triggers the memory growth.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

133.0.3065.92

SDK Version

1.0.3065.39

Framework

Winforms

Operating System

Windows 10

OS Version

10.0.194045

Repro steps

Set up any WebResourceRequestedFilter and an event listener on WebResourceResponseReceived:

webView.CoreWebView2.AddWebResourceRequestedFilter("*", CoreWebView2WebResourceContext.All)
webView.CoreWebView2.WebResourceResponseReceived += OnWebResourceResponseReceived;
private void OnWebResourceResponseReceived(object sender, CoreWebView2WebResourceResponseReceivedEventArgs e)
{
    return;
}

Observing memory usage of renderer process over time (especially with web applications with lots of network requests).

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

Internal Tracking Number: 57210024

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.