Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

By comparing the snapshots you can see which objects were added by the 2nd run. How to link these objects to a memory leak is shown in this nice movie: http://www.red-gate.com/products/ants_memory_profiler/overview.htmImage Removed
Basically it's all about breaking references to never collected (static?) objects.

For me it turned out I had a lot of IDisposable objects (which require you to call Dispose() when you are done) which were not disposed (or the dispose did not clean up all references). By breaking all references to static objects (or other GC-roots) the object will be collected when the garbage man comes around More about disposable here:http://www.eggheadcafe.com/articles/20050625.aspImage Removed