If you want to detect handle leaks in your code than the most simple and
comfortable solution is to use Windows Task Manager and your favourite
Debugger (ex. MSVS Built in Debugger or more powerful WinDbg). In Windows
Task Manager you switch to Processes Tab and localize your app. Then from
menu: View->Choose Presented Info (or something like that) you select
options that want to monitor (ex. Handles,Threads, GDI Objects). Than use
your app and observe if presented values are growing in the time. If yes
then run your app in the debugger and check breakpoints on all functions
that allocate new resources. You observe used resources before enter such
function and after step by the function. If monitored value growed by
executing the function you know that handle/memory/gdi object leak is caused
by the function.
Marcin Zaleczny
Post by kummerI have install the newest version to locate handle leak. Use defautl setings
to monitor the process. But the process exit as soon as it starts.
Why? Is there other alternaltive?