In Development
Last Updated: 16 Mar 2023 13:55 by ADMIN
Created on: 16 Feb 2023 16:54
Category: ListView
Type: Bug Report
Memory leak in ListView when the ItemsSource has changed

Changing the ItemsSource property of the ListView causes it to recreate its cells. The problem is that the existing cells are never reclaimed by the garbage collector, so the memory usage grows constantly. Eventually, the application can run out of memory, if the ItemsSource is updated too many times.

Note: It is possible the memory leak is caused by the bindings holding objects longer than necessary. Similar memory leaks can be reproduced with the .NET MAUI CollectionView as well. Here are a few GitHub issues for the CollectionView that might be related:



Posted on: 13 Mar 2023 06:24

Hello John,

I have sent a reply to the support ticket. The bug is logged for all platforms, there isn't a specific platform mentioned in the bug title.

When a bug is for a concrete platform we added it in the title and shown here: 

Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Posted on: 11 Mar 2023 13:40

This IS an issue on Android why was it declared not to be on the github issue?  It is still occuring with the latest VS and MAUI and after about 17 refreshes of a listview bound to a collection the app becomes unresponsive and quits.  You replicated the issue on Android i mean and then reported to Peppers that it was Windows only. Why?