leaktrap's Introduction

leaktrap

Automatically exported from code.google.com/p/leaktrap

gdi/user handle leak tracking and analysis framework consisting of two components: allocation/deallocation auditing library and a windows debugger extension to manage/analyze and display collected information.

15.10.2010: Workaround that makes the library usable on Windows 7

leaktrap's People

Contributors

leaktrap's Issues

Allow for multiple cleanup functions

Some resources are created using "heterogeneous" functions and can be
deleted through multiple cleanup functions.
Examples:
 HANDLE user32.LoadImage(      
    HINSTANCE hinst,
    LPCTSTR lpszName,
    UINT uType,
    int cxDesired,
    int cyDesired,
    UINT fuLoad
 );
creates handles of 3 (three) different types which are (according to
documentation) should also be removed using a particular cleanup:
Bitmap - DeleteObject
Cursor - DestroyCursor
Icon   - DestroyIcon
but in practice I've seen commercial libraries using DeleteObject for all
cases which leads me to believe it is beneficial that multiple ways to
cleanup are allowed.

Original issue reported on code.google.com by [email protected] on 22 Jan 2009 at 9:16

Recommend Projects