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. Advertising

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.

Share This Page