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

DR
4/15/2008 2:03:59 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() ?

Henning Krause [MVP - Exchange]
4/15/2008 3:08:25 PM

Hi,

answered in public.dotnet.framework.

Please do not multipost. Do a proper crosspost instead.

Kind regards,
Henning Krause

[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 about dotnet performance

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