[BUG] UWP Memory Leak, Page Navigation, CollectionView, BindablePropertyContext

[8m0]

So, the problem in Xamarin not releasing resources. I've seen same bugs in Issues, and it seems no one care about it, but anyway I decided to submit one myself.

It's just a simple app which has About page and a page with CollectionView.
I clicked back and forth between pages 100 times and the program RAM usage rose from 35.8 mb at start, to 315.8:

There is a clean all of mock lists / bindings in OnDisappearing Collection page:

protected override void OnDisappearing()
{
    base.OnDisappearing();
    ((CollectionViewModel)BindingContext).Posts.Clear();
    ((CollectionViewModel)BindingContext).Posts = null;
    ((CollectionViewModel)BindingContext).Posts1.Clear();
    ((CollectionViewModel)BindingContext).Posts1 = null;
    ((CollectionViewModel)BindingContext).Posts2.Clear();
    ((CollectionViewModel)BindingContext).Posts2 = null;

    Collection1 = null;
    Collection2 = null;
    Collection3 = null;

    BindingContext = null;
    CollectionPageView = null;
}

There is another button to call Gc.Collect(), i clicked it 100 times as well. It did some progress for a part only at first click:

Here is screenshot of Debuger window:

Steps to Reproduce

1. Get project from repository https://github.com/8m0/MemoryLeakApp
2. Just click button to navigate to Collection page and then go back multiple times.

Expected Behavior

Release resources, don't save unused objects for no reason.

Actual Behavior

Saves thousands of BindablePropertyContext.

Workaround

If there IS any WORKING workaround which I can test and approve for example on my project provided in the post, please let me know.