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:33:38 -0400
See my reply in other NG.
"Henning Krause [MVP - Exchange]" <newsgroups_remove@xxxxxxxxxxxxxxxxx>
wrote in message news:ujrdaf0nIHA.2632@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
answered in public.dotnet.framework.
Please do not multipost. Do a proper crosspost instead.
Kind regards,
Henning Krause
"DR" <softwareengineer98037@xxxxxxxxx> wrote in message
news:%231405F0nIHA.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: NotifyIcon Menu
- Next by Date: Re: Console Window and XmlSchema
- Previous by thread: Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Next by thread: Windows Update touble
- Index(es):
Relevant Pages
|
|
