Resources to read about Databinding causing memory leaks in WPF?

Answer 1

There are some scenarios which may cause memory leaks in WPF. Here are some references which may help:

http://blogs.msdn.com/jgoldb/archive/2008/02/04/finding-memory-leaks-in-wpf-based-applications.aspx

http://blogs.msdn.com/micmcd/archive/2008/03/07/avoiding-a-wpf-memory-leak-with-databinding-black-magic.aspx

http://support.microsoft.com/kb/938416/en-us

Answer 2

There are quite a few binding scenarios that will cause a memory leak in WPF:

1) Binding to a property on an object that is neither a DependencyProperty or implements INotifyPropertyChanged in any other binding mode than OneTime may result in a memory leak since the first object will be retained in memory for property reference purposes.

2) There's a bug with a TreeView retaining indefinitely a reference to the first selected item. This is due to bug in the CreateUntargetedBindingExpression method that maintains a reference to the first item selected, even though it is an untargeted binding expression. This bug can be worked around with a bit of reflection to precompile the binding expression with a null binding item.