Comments by BeStelios (Top 5 by date)

When i say there is a leak or that the Garbage Collector is simply leaving things behind because they are somehow referenced there is no possibility that my results are inaccurate.

Actually the fact that i created a question means that i have double,triple,x checked.

I know there is a leak because:
Program Starts at 70Mb.
After some scrolls up - down we go to 1.3 GB.
Then a collection is being executed and you can notice the memory Drops to 800-900 where it should be MAX 160-200.

Also keep in mind :
dc.DrawDrawing(PageDraw); // If i do not do this the memory taken increasing and decreasing within reasonable limits and time.
What are the reasonable limits ? -> Without the rendering the Memory with continuous scrolling reaches 400-450 and then drops to 120.

So somehow the drawing after used for render on the framework element is being referenced/weakreferenced EVEN when the element is no longer Visible and even when its property m_PageDraw is null.

*Edit: Also note that the GC might start when the limit is reached (x86 or x64) making the whole OS hang for 1-2 secs.
Rare cases have thrown "out of memory exception" too.