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

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

DR
4/15/2008 2:04:02 PM

dotnet remoting:

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?

eusebiu
5/3/2008 11:06:37 AM

[quoted text, click to view]

Hello... You can use profiler. CLRProfiler (
http://msdn.microsoft.com/en-us/library/ms979205.aspx ) or a
professional one like MemProfiler.