Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- From: "Miha Markic" <miha at rthand com>
- Date: Sun, 20 Apr 2008 10:57:45 +0200
Hi,
The best way would be to use an allocation profiler (i.e. AQTime) - it is the only reliable way to look for memory leaks.
--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/
"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: Rado Ladies Watches Crysma R41762713 - AA - Replica Watch Fake
- Next by Date: Connection works but returns no records
- Previous by thread: Re: GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?
- Next by thread: Querying a Runtime Dataset with LINQ
- Index(es):
Relevant Pages
|
Loading
