GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- From: "DR" <softwareengineer98037@xxxxxxxxx>
- Date: Tue, 15 Apr 2008 14:03:29 -0700
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() ?
.
- Follow-Ups:
- Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- From: Henning Krause [MVP - Exchange]
- Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Prev by Date: Securing a directory and its files with forms authentication
- Next by Date: Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Previous by thread: Securing a directory and its files with forms authentication
- Next by thread: Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Index(es):
Relevant Pages
|