View Single Post
Old 04-15-2008   #2 (permalink)
Scott M.


 
 

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

See my reply in other NG.


"Henning Krause [MVP - Exchange]" <newsgroups_remove@xxxxxx>
wrote in message news:ujrdaf0nIHA.2632@xxxxxx
Quote:

> Hi,
>
> answered in public.dotnet.framework.
>
> Please do not multipost. Do a proper crosspost instead.
>
> Kind regards,
> Henning Krause
>
> "DR" <softwareengineer98037@xxxxxx> wrote in message
> news:%231405F0nIHA.2292@xxxxxx
Quote:

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

My System SpecsSystem Spec