iOS/Catalyst memory leak with CollectionView when CollectionChanged is used

[jonathanpeppers]

Description

This is the latest problem on the issue here: #14654

It can be illustrated with the test: jonathanpeppers@bbea059

When you replace an ItemsSource on iOS, in this way:

var newCollection = new ObservableCollection<string>();
collectionView.ItemsSource = newCollection;
foreach (var item in data)
{
    newCollection.Add(item);
}

It appears that the old items are not removed, the test fails with:

Expected: 3
Actual: 6

But passes on Windows & Android. The test also passes if you change this:

var newCollection = new ObservableCollection<string>();
--collectionView.ItemsSource = newCollection;
foreach (var item in data)
{
    newCollection.Add(item);
}
++collectionView.ItemsSource = newCollection;

However, the sample app still leaks with the above change:

https://github.com/nacompllo/MemoryLeakEverywhere

I've not been successful in solving this one, but it seems good to write down what I found so far.

Steps to Reproduce

Run the test in: jonathanpeppers@bbea059
Or try the sample: https://github.com/nacompllo/MemoryLeakEverywhere

Link to public reproduction project repository

https://github.com/nacompllo/MemoryLeakEverywhere

Version with bug

8.0.0-preview.5.8529

Last version that worked well

Unknown/Other

Affected platforms

iOS, macOS

Affected platform versions

All

Did you find any workaround?

No response

Relevant log output

No response

[ghost]

We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.

[kevinxufei]

According to the project provided by the user, it was verified that there is no memory leak on 17.6.8 (build 400).

[ghost]

Hi @jonathanpeppers. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.

You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.