Memory leak problem - ComponentInputBehavior Q2 2008

2 posts, 1 answers
  1. Cristian Apavaloaiei
    Cristian Apavaloaiei avatar
    25 posts
    Member since:
    Aug 2008

    Posted 17 Jun 2010 Link to this post

    I am currently investigating a memory leak issue in an application using the Telerik Winforms controls version Q2 2008. I think a possible source of the leak to be the elementUnderMouseMonitorTimer field of the ComponentInputBehavior. Was this a known issue for the Q2 2008 release? And if so, what can you recomend me? We have a full telerik license until autumn 2010, so we have access to newer releases but we haven't upgraded yet because the design and functionality of the radcontrols library has changed a lot since q2 2008, and we don't have the time necessary to upgrade the full application.

  2. Answer
    Deyan avatar
    2026 posts

    Posted 23 Jun 2010 Link to this post

    Hello Cristian,

    Thanks for contacting us.

    I would like to inform you that these issues have been addressed and I strongly encourage you to download and install our latest version. We have improved our framework a lot since Q2 2008 in terms of memory footprint and performance. I believe you will benefit from using our latest version and we will be happy to assist you in migrating your application. Please be aware also that we do not provide fixes for older versions.

    Thank you for the understanding and do not hesitate to write back anytime you have further questions or need assistance.

    Kind regards,
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. DevCraft R3 2016 release webinar banner
Back to Top