Win platform WebView cannot be release after its parent window get close

[jingliancui]

Description

Please see the Reproduce

Steps to Reproduce

1. Open the sln using VS 2022
2. Press F5 to start debuging
3. Enter 50 or more to the Entry control
4. Click "new windows" Button
5. Close all WebView windows except the MainPage window

Expect result:
Memory should be reduced

Actual result:
Memory does not get reduced

Link to public reproduction project repository

https://github.com/jingliancui/MAUIWebViewMultipleWinIssue

Version with bug

8.0.40 SR5

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

windows10.0.19041.0

Did you find any workaround?

no

Relevant log output

no

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• WebView MAUI WinUI Memory Leak (#20283), similarity score: 0.79
• Right way to dispose page with WebView (#18021), similarity score: 0.72
• BlazorWebView instances never eligible for garbage collection (#17717), similarity score: 0.72

Closed similar issues:

• [Windows] Webview memory leak (#21194), similarity score: 0.81
• Multi-window memory leak (#10029), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[ninachen03]

Verified this issue with Visual Studio 17.11.0 Preview 1.1 (8.0.40 & 8.0.21). Can repro on windows platform with sample project.

[jingliancui]

@mattleibow @jsuarezruiz @PureWeen
May I know if any workarounds can be used before this gets fix?
For example manually dispose the control or handler etc...

[jonathanpeppers]

@jingliancui for now, can you do something like this in your Page:

    protected override void OnDisappearing()
    {
        base.OnDisappearing();

        webView.Handler?.DisconnectHandler();
    }

(I put x:Name="webView" in the XAML)

This seems to solve the issue in this sample:

[jingliancui]

Hi @jonathanpeppers
PlatformView cannot be null here

not sure which platformview cause this exception

[jingliancui]

@jonathanpeppers You can try my sample repo, it also can reproduce the exception, even I updated the nuget to latest version.

[jonathanpeppers]

This has the fix for the underlying problem, if you are interested:

• [windows] fix memory leak in WebView #23540

It would no longer require DisconnectHandler() to be called.

[jingliancui]

This has the fix for the underlying problem, if you are interested:

• [windows] fix memory leak in WebView #23540

It would no longer require DisconnectHandler() to be called.

Cool! May I know if the fix will be released at next sr8? Thanks