MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Why does WebView2 memory consumption keep increasing?

Open
#2,920 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Repeating Navigate will increase the memory. Is there a way around this?
I tried the following but it didn't work.
・CoreWebView2Profile.ClearBrowsingDataAsync()
・CallDevToolsProtocolMethodAsync("Network.clearBrowserCache", "{}");
Disposing and newing the WebView has no effect.
●Sample Code
キャプチャ
●Sample HTML
キャプチャ3

AB#42189029

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.

Research direction

Start by reproducing repeated Navigate calls with the sample code and HTML, then observe memory while trying ClearBrowsingDataAsync, Network.clearBrowserCache, and WebView disposal. Done would require identifying the cause of the increasing consumption and documenting a verified workaround or explanation; the issue provides no repository files or tests to inspect.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.