Subj : Re: Finding a resource leak using Memproof and Codeguard To : borland.public.cpp.borlandcpp From : "Sebastian Ledesma" Date : Fri Mar 05 2004 11:43 am Richard: Check if you have the latest version, also dont forget to apply any patch to your compiler (if you can upgrade to 5.02 i recommend to do it). Try to make a dummy EvPaint or Paint function in your TMyWindow and check what happens (also in EraseBackground if you have redefined it), (All this assuming that you are using OWL of course). Also you can try en the Memproof newsgroups, Atanas (the author) was always very gentile. news://forums.automatedqa.com/automatedqa.public.memproof Saludos Sebastian "Richard Hufford" escribió en el mensaje news:4047ad92@newsgroups.borland.com... > Thanks, Sebastian. > I don't think the GDI cache explains the problem. If I use the mouse to > drag my window nearly off the screen and then drag it back, I get several > hundred more pointers listed. If I do this again, I get another several > hundred pointers. The pointer count keeps going up, but it never goes back > down. I would think a cache would be fairly stable. > Is this a resource leak? I don't see anything in my code to cause it, but > I'll keep looking. > > .