Leaking pages on navigation

[c-ramarin]

Current behavior

On Android device/emulator, when navigating HomePage -> Page1 and then back to HomePage, then calling GC.Collect (called automatically by HomePage), a reference remains to Page1

Expected behavior

When navigating HomePage -> Page1 and then back to HomePage, then calling GC.Collect, there should be no reference to Page1 and all it's related resources released

How to reproduce it (as minimally and precisely as possible)

UnoAppTest.zip

1- Run app on Android device or emulator in debug mode.
2- Watch the output window in your IDE, notice the Inactive/active DependencyObject references counts
3- navigate to page 1, then page 2, then page 3
4- navigate back to the home page (trigger GC.Collect)
5- notice the IDE output window
6- Reference count = 1 remains for most visited pages (search Page1, Page2, Page3)

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

Android

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[airtaxi]

Could you check this article:
https://platform.uno/docs/articles/features/native-frame-nav.html#platform-specifics

Android: On mobile, the pages in the back stack are still preserved in the visual tree for performance reasons. This feature can be disabled on Android by setting Uno.UI.FeatureConfiguration.NativeFramePresenter.AndroidUnloadInactivePages = true.