VRVijayalakshmi Roopkumar Syncfusion Team September 2, 2015 12:27 PM UTC
Thank you for contacting Syncfusion Support
We are unable to reproduce the reported issue with TabControlExt in our latest version "220.127.116.11". Could you please provide your current product version details, so that it would be very helpful for us proceed on this.
Please let us know if you have any other concern,
Regards, Vijayalakshmi V.R.
SWSwamy September 2, 2015 02:40 PM UTC
We are using version 11.4400.0.26 and used the WinDebug to find the memory leaks.
Please provide the update on this issue with the above version.
VRVijayalakshmi Roopkumar Syncfusion Team September 3, 2015 06:31 AM UTC
Thank you for your update,
We were able to reproduce the reported issue with TabControlExt in the version 11.4400.0.26 and we have fixed this issue internally in our source. A support incident to track the status of this defect has been created under your account. Please log on to our support website to check for further updates
I'm facing similar issue of memory leak using 18.104.22.168. Please provide fix.
VJVictory Jessie Selvam D Syncfusion Team January 29, 2016 11:34 AM UTC
We were unable to reproduce the reported issue "Memory leak in TabControlExt" with 22.214.171.124 version. We have prepared a sample and video to demonstrate the replication steps followed in our side and you can download it from following link:
Please update us the sample along with replications steps for reproducing the issue so that we can proceed further.
RGRajesh GunnamJanuary 29, 2016 11:44 AM UTC
when i do close tab, it is not removing tab item view objects from memory.
VJVictory Jessie Selvam D Syncfusion Team February 1, 2016 11:54 AM UTC
After closing the TabItemExt, TabItemAutomationPeer will hold the instance of TabItemExt and it should be forced to release the memory using FakeWindowAutomationPeer. We have modified the sample for the same and you can download it from the following link: