DependencyProperty Memory leak

Question

I am using PerfView in order to discover memory leaks.

After comparing between two snapshot I noticed that under the tab RefTree -> static vars in PerView. MyPageDependencyProperty of mine takes 78.9% of the Inc%.

The MyPageDependencyProperty should not be there because I closed the the xaml window it is belong to.

I don't use AddValueChanged which can cause memory leak.

The DependencyProperty reveals ObservableCollection<object>.

Does anyone know can I solve this issue?

thanks

I define it by public static readonly DependencyProperty and it points to Public ObservableCollectio — Guy, Nov 14 '13 at 11:03
There you go that is your memory leak. You created a static ObservableCollection. Let me post you an answer that will solve your concerns. — dev hedgehog, Nov 14 '13 at 11:22

score 5 · Answer 1 · answered Nov 14 '13 at 11:24

5

Instead of defining your property like this which creates a static ObservableCollection.

public static readonly DependencyProperty SomePropertyProperty  = DependencyProperty.Register(typeof(..), typeof(..),....,.... , new ObservableCollection<...>());

You should do this:

public static readonly DependencyProperty SomePropertyProperty = DependencyProperty.Register(typeof(..), typeof(..),...., null);

public MyControl()
{
   this.SomeProperty = new ObservableCollection<...>();
}

And your issue will disappear magically. :)

answered Nov 14 '13 at 11:24

dev hedgehog

8,698
3
28
55

I have a question. Static members are associated with their types. so when the application runs, and an object is instantiated of a class, a type instance (i.e., Foo+<>c) is created as well in the memory along with its static members, right? so when a normal instance of the class is not in use, why GC is not able to remove it from the memory? I feel there is something missing I cannot grasp the whole idea. – Abdulkarim Kanaan Jul 20 '18 at 04:31

score -3 · Answer 2 · edited May 23 '17 at 12:26

-3

This may be because of CLR has the links to the object somewhere and it doesn't Dispose. Try to force Garbage collector to run and track what will happen.

edited May 23 '17 at 12:26

Community

1
1

answered Nov 14 '13 at 09:37

I did GC.Collect(MaxGeneration,Forced) GC.WaitForPendingFinalizers) Still There – Guy Nov 14 '13 at 09:49
Whatever, memory leaks are always caused by hanging references – Nov 14 '13 at 10:18

DependencyProperty Memory leak

2 Answers2