We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Memory Leak

Thread ID:

Created:

Updated:

Platform:

Replies:

32605 Aug 4,2005 08:33 AM Mar 25,2008 05:35 AM General Discussion 3
loading
Tags: General Discussion
Albert Brown
Asked On August 4, 2005 08:33 AM

Hello We work with Synchfusion essential suite version 2.1.0.9 and we’ve faced with a severe memory leak problem throughout our application causing from Synchfusion components. Some results from memory profiler come below: Namespace Name Instance Common.Uil.Controls RToLPanel #437,863 Common.Uil.Controls RToLPanel #437,872 System.Windows.Forms Panel #437,874 Syncfusion.Windows.Forms.Tools TabControlAdv #437,875 System EventHandler #439,026 System EventHandler #446,083 Syncfusion.Windows.Forms Office2003Colors MenuColorsChanged Namespace Name Instance Syncfusion.Windows.Forms.Tools.XPMenus BarControlInternal #437,013 System EventHandler #444,132 Syncfusion.Windows.Forms MenuColors MenuColorsChanged These problems seem to have a common root. In order to change theme and colors for components, Synchfusion has defined some static events (like Office2003Colors) and all components register themselves to these events, so that when a theme is changed all components are informed. The problem is that as the event is static the reference for the registered component is not freed and so the component is never garbage collected. Would you tell us if this bug is fixed in newer versions of Synchfusion? If not, what we can do to solve this memory leak problem in our application? Needless to say this Problem is getting more and more critical for us. Yours truly, Ershad Rahimikia

Administrator [Syncfusion]
Replied On August 4, 2005 11:39 AM

Hello Ershad, Thank you for bringing this issue to our attention. With the information you provided, I''ve just opened a support incident in your Direct-Trac account. There, you can correspond directly with our support team and upload any relevant samples or screenshots. For help with logging into your personal support account, please contact salessupport@syncfusion.com. We look forward to quickly resolving this issue. Thank you very much for your use of Syncfusion products. Best regards, Sierra >Hello > >We work with Synchfusion essential suite version 2.1.0.9 and we’ve faced with a severe memory leak problem throughout our application causing from Synchfusion components. >Some results from memory profiler come below: > >Namespace Name Instance > >Common.Uil.Controls RToLPanel #437,863 >Common.Uil.Controls RToLPanel #437,872 >System.Windows.Forms Panel #437,874 >Syncfusion.Windows.Forms.Tools TabControlAdv #437,875 >System EventHandler #439,026 >System EventHandler #446,083 >Syncfusion.Windows.Forms Office2003Colors MenuColorsChanged > >Namespace Name Instance >Syncfusion.Windows.Forms.Tools.XPMenus BarControlInternal #437,013 >System EventHandler #444,132 >Syncfusion.Windows.Forms MenuColors MenuColorsChanged > >These problems seem to have a common root. In order to change theme and colors for components, Synchfusion has defined some static events (like Office2003Colors) and all components register themselves to these events, so that when a theme is changed all components are informed. The problem is that as the event is static the reference for the registered component is not freed and so the component is never garbage collected. >Would you tell us if this bug is fixed in newer versions of Synchfusion? If not, what we can do to solve this memory leak problem in our application? Needless to say this >Problem is getting more and more critical for us. > >Yours truly, >Ershad Rahimikia > > > > >

Steven Knauber
Replied On March 12, 2008 02:19 PM

My company uses Syncfusion essential suite version 2.1.0.21. We have the same problem and I am wondering if there is a fix or suggestion to unhook Syncfusion control event subscriptions to objects like Office2003Colors.

I know you can unhook these by explicitly calling Dispose() on all the Syncfusion controls when you are done with them. In fact, I have written a utility function that I can call on a form or control that has nested child controls. It will search through the hierarch of child controls and dispose of any that are of the "Syncfusion" namespace(using reflection). This will prevent hidden memory leaks due to forms that you thought should have been garbage collected, but were not due to the Syncfusion events. This method is a little slow and also requires the programmer to remember to do this everytime he is done with a form or control.

If you can suggest a better way, it would be greatly appreciated. For instance, is there a way to globally turn off these event subscriptions?

Steve Knauber

>Hello
>
>We work with Synchfusion essential suite version 2.1.0.9 and we’ve faced with a severe memory leak problem throughout our application causing from Synchfusion components.
>Some results from memory profiler come below:
>
>Namespace Name Instance
>
>Common.Uil.Controls RToLPanel #437,863
>Common.Uil.Controls RToLPanel #437,872
>System.Windows.Forms Panel #437,874
>Syncfusion.Windows.Forms.Tools TabControlAdv #437,875
>System EventHandler #439,026
>System EventHandler #446,083
>Syncfusion.Windows.Forms Office2003Colors MenuColorsChanged
>
>Namespace Name Instance
>Syncfusion.Windows.Forms.Tools.XPMenus BarControlInternal #437,013
>System EventHandler #444,132
>Syncfusion.Windows.Forms MenuColors MenuColorsChanged
>
>These problems seem to have a common root. In order to change theme and colors for components, Synchfusion has defined some static events (like Office2003Colors) and all components register themselves to these events, so that when a theme is changed all components are informed. The problem is that as the event is static the reference for the registered component is not freed and so the component is never garbage collected.
>Would you tell us if this bug is fixed in newer versions of Synchfusion? If not, what we can do to solve this memory leak problem in our application? Needless to say this
>Problem is getting more and more critical for us.
>
>Yours truly,
>Ershad Rahimikia
>
>
>
>
>


Administrator [Syncfusion]
Replied On March 25, 2008 05:35 AM

Hi Steven, Thanks for your feedback on this issue. This is a known issue in the XPMenus framework and we have been successful in eliminated all the leaks caused by the MainFrameBarManager from the version 4.2.0.37. Please refer the following defect report in the following link: http://www.syncfusion.com/support/issues/tools/Default.aspx?ToDo=view&questId=432 We are glad to inform you that we have fixed many defects and added new features with our latest public release Essential Studio 2008 Volume 1. I would like to recommend you to upgrade to this version. http://www.syncfusion.com/downloads/latestversion/default.aspx Unlock key : If your Essential Studio license is current, you will be able to obtain the key to install this version from your account in DirectTrac. Otherwise please contact your Syncfusion Sales Representative or e-mail salessupport@syncfusion.com. Please let me know if any concerns. Regards, Fathima.

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;