BoldSignEasily embed eSignatures in your .NET applications. Free sandbox with native SDK available.
I discovered a memory leak of SfTabView control. I used a simple test app with two pages. The second page contains only tabview with 2 empty tabs. I wrote a loop for navigation from first page to second one and back about 30 times.
The memory consumption increases with every next navigation forth and back, starting from a couple megabytes up to tens megabytes.
Then I deleted SfTabView control from the second page to make it absolutely clean, and repeated the test. In this case there’s no memory leak.
More over, If tabs of tabview contain inner content, the memory leak increases in geometrical progression. Although test with that content w/o tabview control doesn’t cause the memory leak.
In my real app I have a tabview with 4 tabs. Each tab contains a listview with hundreds of items (labels and images). After a series of navigation to and from, memory consumption increases up to several hundreds of megabytes. The app becomes unresponsive and finally crashes.
Tested on the Samsung Galaxy Note 10 Plus, Android 10.
Xamarin Forms version 18.104.22.1681537Syncfusion version 22.214.171.124
Hi Konstantin,Greetings from Syncfusion.
We have analyzed your query and we could able to reproduce the reported issue of “Memory leak in Tab View”. We have logged a defect report regarding on this and it can be tracked through our feedback portal below.
This fix will be included in our upcoming weekly Nuget release which is expected to be rolled out on 11th February 2020.
Please let us know if you have any concern.Regards,Hemalatha M.
Would be possible to have the solution for this issue "Memory leak in Tab View”. sooner than the end of March?
Hi Viseo, Konstantin,
Thanks for your update.
Since the issue are having also in Xamarin forms custom controls, we will analyze more and fix this issue. We will fix and provide patch for this on March 10th, 2020.