debugging a resource leak in a printer driver

Posted by MK on Stack Overflow See other posts from Stack Overflow or by MK
Published on 2010-04-21T21:59:04Z Indexed on 2010/04/21 22:03 UTC
Read the original article Hit count: 384

I'm trying to debug a memory leak in a printer driver. I'm pretty sure it's a resource leak, not just a plain memory leak because analyzing heap with !heap -s in windbg doesn't show any increase. How do I monitor other kinds of objects with windbg? Number of GDI objects and open handles is not growing either, so what could it be?

© Stack Overflow or respective owner

Related posts about debugging

Related posts about memory-leaks