[Solved] Memory leak in RadListView

1 Answer 244 Views

ListView TabView

This question is locked. New answers and comments are not allowed.

Didi

commented on 22 Jul 2022, 06:18 AM

Could you please share on which platform the behavior occurs? I am asking as we have a memory leak report for RadListView inside RadTabView on UWP. https://feedback.telerik.com/xamarin/1550021-listview-uwp-memory-leak-when-the-control-is-inside-a-tabview

Looking forward to your reply.

Nik

commented on 25 Jul 2022, 01:39 PM | edited

We are using UWP platform, we are already using IsContentPreserved property workaround suggested in the link you provided above. however the memory leak issue still persists.

do you suggest any other workaround for this issue? are you planning on releasing any hotfix any sooner for the memory leak issue.

1 Answer, 1 is accepted

answered on 27 Jul 2022, 08:03 AM

Hi Nikhil,

I've just raised the priority of the issue per your report, still, for the time being, I cannot commit to a certain timeframe for providing a fix.

The usage of IsContentPreserved property improves the memory statistics on our side when researching the case. Could you let me know how exactly you're testing the memory leak?

In general, memory leaks are tested inside the Visual Studio (Diagnostic Tools) and you can take snapshots there and compare the information in the snapshots (2, 3 snapshots). It is important to call GC.Collect() before the snapshot. The app should be built in release mode. Did you try this approach?

Regards,
Yana
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Nik

commented on 27 Jul 2022, 09:06 AM

We are testing the memory leak by checking the memory usage in the task manager and also in visual studio's diagnostic tool(Release Mode).

Yana

commented on 28 Jul 2022, 10:30 AM

Hi Nikhil,

Memory usage is task manager cannot be considered as a memory leak - memory leaks have to be tested inside Visual Studio Diagnostic Tools. Our tests show the TabView.IsContentPreserved does not remove the memory lea, still it definitely reduces the memory usage, that's why I suggested it as a temporary workaround.

Please follow the feedback item on the issue to get notified on any status changes. I am sorry for the caused inconvenience.