Is That a WeakReference In Your Gen 2 or Are You Just Glad to See Me?(www.wintellect.com)

submitted by dpetersondpeterson(4397) 6 months, 24 days ago

John Robbins walks us through debugging an application which is not clearing its memory during garbage collection due to WeakReferences. He shows us how to use the tools available to us to trace the memory problem all the way back to the source.

2 comments |category: |Views: 81

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by vijaystvijayst(1311) 6 months, 23 days ago 0

Memory leaks are tough to track down. There are other profilers like ANTS which are easier to use.

Reply

posted by NoldorinNoldorin(829) 6 months, 22 days ago 0

This is strange... I don't quite get it. Surely WeakReferences only encourage/ensure earlier garbage collection? How can they create memory leaks?

Reply

information Login or create an account to comment on this story