Jonathan Peppers

We tried to put a disclaimer on this project, just fyi: 

Yes, we made this primarily for Android, and I believe a contributor added Mac & iOS.

Does this still happen if you're only building `net6.0-android` as a single `$(TargetFramework)`? (remove any `monoandroid`) One thing you could try as a workaround is to add a target like:...

Ok, I think I see the pattern that isn't currently caught by the analyzer: ```csharp class Foo { UIButton bar = new(); public Foo() { bar.TouchUpInside += OnTouch; } void...

Ok, the simple example above, `Foo`, does not appear to leak in isolation: https://github.com/jonathanpeppers/MemoryLeaksOniOS/compare/UIButtonEvents So, this must only happen with MAUI `IPlatformViewHandler` types? There must be something that causes a...

I think there is a general issue if you do: ```csharp // AppShell lives forever App.Current.MainPage = new AppShell(); App.Current.MainPage = new ContentPage(); ``` I think `AppShell` has some circular...

If you only have one `AppShell` instance in the entire app, any sub pages should be able to go away just fine. If you need to change `Application.MainPage`, you could...

@ESO-ST if you are just navigating to a page and then navigate back (so it is popped), then those pages should go away. If you have at least one `GC.Collect()`...

@ESO-ST looking at your sample, it is a bunch of tabs: * https://github.com/ESO-ST/WebViewCrashMidLoad/blob/MemoryLeak/WebViewCrashMidLoad/AppShell.xaml Pages would go away if you navigate away from them, but changing tabs is different. I think...

For pages displayed as a tab, it appears the behavior is they will stay around. Xamarin.Forms had some logic that was a little different: it would keep 3 pages around...