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

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DR - 15 Apr 2008 22:03 GMT

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

Reply to this Message

Henning Krause [MVP - Exchange] - 15 Apr 2008 23:08 GMT

Hi,

answered in public.dotnet.framework.

Please do not multipost. Do a proper crosspost instead.

Kind regards,
Henning Krause

> GC.Collect() not cleaning memory, how to find out what references to lots
> of memory still exist?
[quoted text clipped - 6 lines]
> easy way to see what references that I forgot to set to null so that the
> memory cleas up on GC.Collect() ?

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...