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

Discussion in 'ASP .Net Building Controls' started by DR, Apr 15, 2008.

  1. DR

    DR Guest

    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() ?
     
    DR, Apr 15, 2008
    #1
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. DR
    Replies:
    0
    Views:
    817
  2. brad
    Replies:
    9
    Views:
    606
    Bruno Desthuilliers
    Jun 19, 2008
  3. DR
    Replies:
    0
    Views:
    896
  4. DR
    Replies:
    1
    Views:
    358
    Henning Krause [MVP - Exchange]
    Apr 15, 2008
  5. DR
    Replies:
    0
    Views:
    289
  6. DR
    Replies:
    1
    Views:
    429
    Scott M.
    Apr 16, 2008
  7. Alan Howard
    Replies:
    1
    Views:
    190
    Jonathan Wood
    Mar 7, 2004
  8. coolneo
    Replies:
    9
    Views:
    450
    coolneo
    Jan 30, 2007
Loading...