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

Guest

Posts: n/a

04-15-2008

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() ?

Thread Tools
Show Printable Version Email this Page

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Trackbacks are On Pingbacks are On Refbacks are Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?	DR	ASP .Net Web Services	1	04-15-2008 11:32 PM
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?	DR	ASP .Net Security	1	04-15-2008 09:50 PM
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?	DR	ASP .Net Web Controls	0	04-15-2008 09:03 PM
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?	DR	ASP .Net Mobile	0	04-15-2008 09:03 PM
GC.Collect() not cleaning memory, how to find out what references to lots of memory still exist?	DR	ASP .Net Building Controls	0	04-15-2008 09:03 PM