[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.aspnet.caching

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

Daniel

4/15/2008 9:03:00 PM

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() ?


1 Answer

Alvin Bruney [ASP.NET MVP]

4/20/2008 10:17:00 PM

0

stop multi posting please.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
-------------------------------------------------------




"DR" <softwareengineer98037@yahoo.com> wrote in message
news:OxNUAD0nIHA.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() ?
>