A class for helping track down GDI leakshttp://blogs.msdn.com/jfoscoding/archive/2005/02/03/366430.aspxFinding leaks This article describes the various methods for tracking down GDI and User handle leaks. Unfortunately in Win2k/XP you cannot tell which kind of handles are out (windows 9x used to distinguish) - however I haven't usually needed to know thisen-USCommunityServer 2.1 SP1 (Build: 61025.2)Articles as seen on jfo's codinghttp://blogs.msdn.com/jfoscoding/archive/2005/02/03/366430.aspx#458764Thu, 01 Sep 2005 02:27:25 GMT91d46819-8472-40ad-a661-2c78acb4018c:458764jfo's codingCustom PaintingPainting best practices ComboBox OwnerDrawLayoutDock layout/Using the Splitter control...You gotta learn to let it go: Top 4 memory leakshttp://blogs.msdn.com/jfoscoding/archive/2005/02/03/366430.aspx#594865Thu, 11 May 2006 00:06:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:594865jfo's codingI got a note from Mukund, who is investigating a memory leak problem.&amp;amp;nbsp; <br> <br>Hi Jessica, Is it true...Rule of thumb for System.Drawinghttp://blogs.msdn.com/jfoscoding/archive/2005/02/03/366430.aspx#677946Tue, 25 Jul 2006 18:15:58 GMT91d46819-8472-40ad-a661-2c78acb4018c:677946jfo's codingA friend of mine ran into this the other day. <br>If you call a method to get a handle some sort of System.Drawing...