You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cuiliang
changed the title
[Problem/Bug]: Memory leak? WebView2 and parent window not released after closed
[Problem/Bug]: Memory leak? WebView2 and parent window not released after close
Jan 10, 2024
@vbryh-msft Besides, if the HostObject used in AddHostObjectToScript() hode a reference of host window, there will be another
referenct path live after window closed.
@cuiliang We've fixed the issue in Edge canary 126.0.2536.0+. Please test and let us if WV2 objects are still leaking.
Also, there is a small issue in WebView2WpfBrowser where the code isn't calling webView.Dispose() upon Close WebView. We'll soon push that sample app fix to our public repo but please call WV2 dispose for testing.
What happened?
Using the smaple application: https://github.com/MicrosoftEdge/WebView2Samples/tree/main/SampleApps/WebView2WpfBrowser
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
120.0.2210.121
SDK Version
1.0.2210.55
Framework
WPF
Operating System
Windows 11
OS Version
No response
Repro steps
See issue description.
Repros in Edge Browser
No
Regression
No, this never worked
Last working version (if regression)
No response
AB#48526819
The text was updated successfully, but these errors were encountered: