Is there any known memory leak issue related to using the custom WPF window chrome?
We have applied it to all of our windows and find that memory is not being released. Transient windows (dialogs) are opened and closed, all the usual window close events fire, but over the course of using our application for a couple of hours memory usage climbs and performance degrades. Simply removing the chrome seems to solve this issue.
We have declared 2 instances of WindowChrome as static resources and all views bind to these (one for windows with an icon and one for those that don't have an icon).
We are using the Metro Dark theme.
Memory profiling points to an event called RenderPropertyChanged.
Is there anything that sounds wrong with our setup or are there suggestions for working around this issue (short of removing the chrome)?