Memory leak

6 posts, 1 answers
  1. Gianpaolo
    Gianpaolo avatar
    9 posts
    Member since:
    Nov 2013

    Posted 30 Jan 2014 Link to this post

    Hello,

    I'm experiencing a memory leak when using RadPropertyGrid in a project targeting .Net Framework 4.
    I would attach a sample project to demonstrate the issue, but apparently only images can be attached.
    I'm able to reproduce the issue with a simple project containing a main window with a button opening a new window with only a RadPropertyGrid, with Item set to a simple POCO object with 2 string properties. The window is not released when closed.
  2. Yordanka
    Admin
    Yordanka avatar
    634 posts

    Posted 31 Jan 2014 Link to this post

    Hi Gianpaolo,

    Thank you for the feedback.

    I've tested the problem with Q3 2013 SP2 official binaries and I couldn't reproduce the mentioned leak. Please check the attached test project. I used JustTrace memory profiler.

    Regards,
    Yordanka
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  3. UI for WPF is Visual Studio 2017 Ready
  4. Gianpaolo
    Gianpaolo avatar
    9 posts
    Member since:
    Nov 2013

    Posted 31 Jan 2014 in reply to Yordanka Link to this post

    Hi Yordanka,

    I can confirm the leak on my system with the project you attached. I used both .Net Memory Profiler and CLR Memory profiler.

    I'm running Windows 7 with .Net Framework 4.5. Let me know if you need more information on my system.

    I have attached to screenshots with the snapshots taken with .Net Memory profiler with and without the RadPropertyGrid.
  5. Answer
    Yordanka
    Admin
    Yordanka avatar
    634 posts

    Posted 03 Feb 2014 Link to this post

    Hello Gianpaolo,

    Thank you for the details.

    Indeed, there is a problem and I logged it for further investigation. We will do our best to address it after Q1 official release.

    I've updated your Telerik points.

    Regards,
    Yordanka
    Telerik
    TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
    Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
    Sign up for Free application insights >>
  6. Nate
    Nate avatar
    7 posts
    Member since:
    Mar 2015

    Posted 27 Mar 2015 Link to this post

    Has this been addressed yet? Is there a workaround? How do I know if my PropertyGrids are being affected by this (or if there's another cause to my memory leaks)?
  7. Dimitrina
    Admin
    Dimitrina avatar
    3769 posts

    Posted 30 Mar 2015 Link to this post

    Hello,

    The memory leak discussed in this thread was successfully resolved with version Q2 2014. Would you please test with the latest version of UI for WPF to ensure it works fine now?

    Regards,
    Dimitrina
    Telerik
     

    See What's Next in App Development. Register for TelerikNEXT.

     
Back to Top
UI for WPF is Visual Studio 2017 Ready