TabView breaks Navigation and causes memory leaks.

[Noemata]

Describe the bug
Just by adding the TabView control to a page, it breaks Navigation and causes memory leaks.

Steps to reproduce the bug

App2.zip

Steps to reproduce the behavior:

1. Build App attached above.
2. Run App.
3. Select Page navigation buttons and observe Page deconstructors being called.
4. Close App.
5. Uncomment TabView control on Page 1 Xaml.
6. Run App.
7. Select Page navigation buttons and observe Page 1 deconstructor not being called causing memory leaks.

Expected behavior

Page 1 deconstructor should be called so its memory resources can be reclaimed.

Screenshots

n/a

Version Info

NuGet package version:
[Microsoft.UI.Xaml.2.6.0-prerelease.210315002]

Windows 10 version	Saw the problem?
October 2020 Update (19042)	Yes

Device form factor	Saw the problem?
Desktop	Yes

Additional context
This issue affects every release of the TabView control, including those in the Community Toolkit, so the problem predates integration into WinUI.

[lukeblevins]

#3597

Could this be related to the issue I reported last year?

[Noemata]

@duke7553 , I wouldn't be able to speculate on that. Just adding the control and not using it was enough to cause Navigation to leak. Have a look at the code. I don't have much experience with the control, I was looking into an issue someone else had posted. Would be helpful to have other eyes on the code samples.

There are curious interactions with Navigation Frame and NavigationCacheMode. NavigationCacheMode="Enabled" seems to trigger a memory leak regardless of what controls you are using. TabView seems to have additional problems.

For additional context, you can look here: #4713

[Noemata]

The following testing tool is mostly self explanatory if you have a close look at the code: https://github.com/Noemata/RosettaNavigation

The tool may be used to test both performance and Navigation Frame memory issues for both WinUI and UWP.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days.