By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,246 Members | 1,553 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,246 IT Pros & Developers. It's quick & easy.

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

P: n/a
Hi,

answered in public.dotnet.framework.

Please do not multipost. Do a proper crosspost instead.

Kind regards,
Henning Krause

"DR" <so*******************@yahoo.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
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() ?
Jun 27 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
See my reply in other NG.
"Henning Krause [MVP - Exchange]" <ne***************@this.infinitec.de>
wrote in message news:uj**************@TK2MSFTNGP04.phx.gbl...
Hi,

answered in public.dotnet.framework.

Please do not multipost. Do a proper crosspost instead.

Kind regards,
Henning Krause

"DR" <so*******************@yahoo.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
>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() ?

Jun 27 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.