When you close the window, this still exist in memory.
Demonstration sample project is in attachment.
For better demonstration, window containts largeArray (50 MB).
I found solution:
dockingManager must be removed from parent control on closed window event, because this is not removed automatically.
```
private void Window_Closed(object sender, EventArgs e)
{
parentOfDockingManager.Children.Remove(dockingManager);
}
```
My question is:
Is this recommended behaviour or issue?
Comments: ** Comment from web user: kram127 **
Demonstration sample project is in attachment.
For better demonstration, window containts largeArray (50 MB).
I found solution:
dockingManager must be removed from parent control on closed window event, because this is not removed automatically.
```
private void Window_Closed(object sender, EventArgs e)
{
parentOfDockingManager.Children.Remove(dockingManager);
}
```
My question is:
Is this recommended behaviour or issue?
Comments: ** Comment from web user: kram127 **
I am investigating memory leak issue in our application, and found out the same thing.
The resolution will not work if there are any control in the DockingManager (.xaml) with an event.
I managed to get rid of the memory leak by manually unsubscribing to each control events within each tabs, but that is not very maintable...