Memory Leak on closing form

[Remigio Fattori]

Hi,

i'm using RibbonControlAdv with TabbedMDIManager.

Switching from two or more forms (tab), the form is disposed but not garbage collected. This not happen if the form is closed without having changed form (tab)

Looks like the private variable TabList of RibbonControl not release the form reference. Attached you can find picture from memory profiler.

Thank you

Attachment: RibbonLeak_40107e61.7z

[Arulraj A]

Hi Remigio 

Thank you for contacting Syncfusion Support.                                                                                               

We have checked the reported scenario with RibbonControlAdv and we were able to observe that the MergeTabInfo instance hold on switching the forms[tabs] at our end. We have logged a defect report on this and the fix will be available in our upcoming 2018 Volume 4 release which is expected at end of December 2018. 

Regards, 

Arulraj A 

[Remigio Fattori]

Thank you!

I'll wait the release

[Remigio Fattori]

Hi Remigio 

Thank you for contacting Syncfusion Support.                                                                                               

We have checked the reported scenario with RibbonControlAdv and we were able to observe that the MergeTabInfo instance hold on switching the forms[tabs] at our end. We have logged a defect report on this and the fix will be available in our upcoming 2018 Volume 4 release which is expected at end of December 2018. 

Regards, 

Arulraj A 

Hi,

looks like the problem is still here in the latest version...

[Jagadeesan Pichaimuthu]

Hi Remigio,

Sorry for the inconvenience caused.

While fixing the reported “Memory leak occurred while switching the tabs in Ribbon” problem, some of the important features in RibbonControlAdv getting affected due to this fix. So we are try to fix the reported issue in our upcoming Volume 2 Release which is expected to be available in the end of June 2019.

We appreciate your patience until then.

Regards, 

Jagadeesan 

[Remigio Fattori]

Thank you

[Jagadeesan Pichaimuthu]

Hi Remigio, 

 

Thanks for your update. 

 

As promised earlier, we will include the issue fix in our 2019 Volume 2 main release which is scheduled to be rolled out by end of June 2019. 

 

We appreciate your patience until then. 

 

Regards, 

Jagadeesan