Three Common Causes of Memory Leaks in Managed Applications

posted by  varson (7)  13 months ago (blogs.msdn.com)

One of the joys of working with managed code is not having to worry (as much) about memory management and letting the Garbage Collector do it's job.  There are situations, however, when applications need to take a more active role in memory management.  At MEDC 2005, I spoke, during my debugging session, about three common causes of memory leaks in managed applications:

1. Holding references to managed objects
   
2. Failing to release unmanaged resources
   
3. Failing to dispose Drawing objects

Holding references to managed objectsI do not actuall