Memory Leak Related to WindowChrome?

Hi Jay,

We aren't aware of any leaks but I do wonder if the way you are doing things is potentially causing problems.  We don't recommend reusing instances of WindowChrome.  I would try switching it so that each Window has its own WindowChrome instance and see if that resolves the issue for you, since that's the intended use of that class.

Okay, we'll try that.

It is worth noting that the Window Chrome topic in the Actipro Themes documentation says WindowChrome can be shared as a static resource:

You could also apply the chrome to windows in an app by defining the chrome in your Application.Resources with an x:Key. Then reference that chrome in each Window's XAML like:

<Window xmlns:themes="http://schemas.actiprosoftware.com/winfx/xaml/themes"
    ...
    themes:WindowChrome.Chrome="{Static YourWindowChromeKeyHere}">
    ...
</Window>

We found that not sharing the resource resolved the issue.

Rather than declaring a new WindowChrome for all windows, we just went to the resource and added x:Shared="False". It would be great if this tidbit could be added to the docs.

Thanks for your help!

Hi Jay,

I wanted to follow up.  We did some more looking into this and you can reuse an instance of WindowChrome across the various Windows but if you do that, be sure to clear the chrome reference as the window is closing for the last time and before the reference to it is lost.  For instance, you could do this in your Window's OnClosed override:

WindowChrome.SetChrome(this, null);