Freeing Memory on Close

2 posts, 0 answers
  1. Mark
    Mark avatar
    32 posts
    Member since:
    Jan 2012

    Posted 13 Sep 2012 Link to this post

    Hi,

    I am using v.2012.2.726.40 and note there are a number of other queries regarding memory allocation with RadDock on here but can't find anything that quite matches my question.

    I have a RadDock control that contains DockWindows. These are left as default except CloseAction is DockWindowCloseAction.CloseAndDispose

    The problem I am experiencing is when I close any window via the drop down menu on the RadDock (Close, Close All But This, Close This) the tab closes, the Closing and Closed events are fired (which perform some bespoke clean up) and the memory for the window is released. When I close the window by clicking the "x" on the window, again the Closing and Closed events fire, however the memory is does not appear to be released.

    I am unable to trace any difference between the two operations, so could you let me know whether the close is performed any differently depending on whether initiated from the menu or the close icon?

    Many thanks,

    Mark.
  2. Ivan Todorov
    Admin
    Ivan Todorov avatar
    688 posts

    Posted 18 Sep 2012 Link to this post

    Hello Mark,

    Thank you for contacting us.

    I have tried to reproduce your scenario but I was not able to observe the described behavior. Whichever close method I choose, the document windows are released from memory. Therefore, I would kindly ask you to send us a sample project which demonstrates this behavior. This will let us investigate it and isolate any potential memory leaks.

    Looking forward to hearing from you.

    Greetings,
    Ivan Todorov
    the Telerik team
    RadControls for WinForms Q2'12 release is now live! Check out what's new or download a free trial >>
  3. UI for WinForms is Visual Studio 2017 Ready
Back to Top