Dear support team,
attached is an example solution which causes on our machines the effect that the DockManager allocates memory for the tabs but dont release it when the tab is closed.
Hello,
I have been looking into your question and you may try to dispose a content pane on closing handling its ’Closing’ event like:
private void PaneClosing(object sender, PaneClosingEventArgs e)
{
Dispatcher.BeginInvoke(new Action(() =>
GC.Collect();
GC.WaitForPendingFinalizers();
}), System.Windows.Threading.DispatcherPriority.Background);
}
Please in future create a separate thread for each of your new question.
Hope this helps you.
I think i have the same problem as mentioned in this post. I have recently downloaded a source project from http://brianlagunas.com/xamdockmanager-prism-region-adapter-update-3/. I found this is very useful as it is implemented using prism concept. I made some changes on this source code and I tested the memory usage using memory profiler. fyi, My company is currently using Infragistics product.
I found that when closing the Pane from the UI, sometimes it can be disposed successfully, sometimes it is can't. Here i attached the source code with the changes i made. How can i ensure that the content pane can be disposed properly when it is closed? I have posted the same problem in http://brianlagunas.com/xamdockmanager-prism-region-adapter-update-3/. Hope to hear from you soon.
Thank you.
I am just checking if you require any further assistance on the matter.
Thank you for your post. I have been looking into your issue and I was wondering why you are thinking that there is memory leak when you close the content panes. When a content pane is close it is removed from the panes collection of the TabGroupPane.
Looking forward to hearing from you.