Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- From: "Scott M." <smar@xxxxxxxxxxxxx>
- Date: Tue, 15 Apr 2008 19:32:18 -0400
Calling GC.Collect is a bad idea is all but the most severe cases. In real
practice, you should not use it as it can actually impede your application's
performance.
Your best bet is to look carefully at the objects you are using and make
sure that, where appropriate, you call Dispose on them.
-Scott
"DR" <softwareengineer98037@xxxxxxxxx> wrote in message
news:uOkNbC0nIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
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() ?
.
- References:
- Prev by Date: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Next by Date: Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Previous by thread: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- 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
|