Question

today my application throw a "no more handles" error on Windows, while allocating an image. To debug this I would love to get a list of all handles my application has aquired. If possible even with type, like font, image or whatever, and include the information in my error report to see where my application leaks.

I use Java and SWT, but have no problem with calling native functions or a third-party application to fetch the information in this case.

Was it helpful?

Solution 2

GDIView was the tool I needed! It is even scriptable, so the output can be used in bug reports.

OTHER TIPS

For a utility, try Process Explorer from Microsoft Sysinternals. This will show process strings, handles, files, parents, threads, thread stacks, etc., etc.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top