[Core] Changes disposing items in CollectionView #10590
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Changes (disconnecting and disposing Handlers) disposing items in Windows CollectionView.
Testing with a CollectionView having 1000 items scrolling up and down. This is the current behavior:
After the changes:
The memory consumption and the references count is much lower with the changes.
Forcing a GC.Collect doing scroll:
We can see how memory is constantly collected and in this case the memory does not increase.
Issues Fixed
Fixes #10560