What are the challenges you face when working across database platforms? Take the survey

How to find the cause of StreamAsIStream leak

alexbusteedalexbusteed Posts: 2
edited September 10, 2010 8:03AM in ANTS Memory Profiler Previous Versions
I am writing a mixed WPF / Winforms application and find that when I create a new WPF view and present it using ElementHost, that two 5.04 MB byte[] objects are created on the Large Object Heap and are never disposed.

Using ANTS Memory Profiler 5.2, I see the object retention graph for these as showing:
    System.Byte[] (the object in question) System.IO.MemoryStream System.Windows.Media.StreamAsIStream GC Handle

I have filtered using "Kept in memory only by GC roots of type: COM+ (all other types were unticked).

According to other posts (e.g http://www.red-gate.com/MessageBoard/viewtopic.php?t=9521) this points at a native leak. But... I'm not sure how to progress.

Can anyone advise on how I can identify the source of the leak?

Many thanks


Sign In or Register to comment.