GC.Collect() not cleaning memory, how to find out what references to lots of
memory still exist?

When all my processign is done i set everything to null and then:
GC.Collect();
and then
GC.WaitForPendingFinalizers();
but it still shows that my process takes 400 MB of memory. Is there any easy
way to see what references that I forgot to set to null so that the memory
cleas up on GC.Collect() ?

Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist? by Scott

Scott
Tue Apr 15 18:33:11 CDT 2008

See my reply in other NG.


"DR" <softwareengineer98037@yahoo.com> wrote in message
news:uEkRnF0nIHA.2292@TK2MSFTNGP03.phx.gbl...
> GC.Collect() not cleaning memory, how to find out what references to lots
> of memory still exist?
>
> When all my processign is done i set everything to null and then:
> GC.Collect();
> and then
> GC.WaitForPendingFinalizers();
> but it still shows that my process takes 400 MB of memory. Is there any
> easy way to see what references that I forgot to set to null so that the
> memory cleas up on GC.Collect() ?
>