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

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

DR
4/15/2008 2:03:19 PM

asp.net caching: 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?

Alvin Bruney [ASP.NET MVP]
4/20/2008 6:17:29 PM

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
-------------------------------------------------------

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the asp.net caching group.