I've got a memory leak issue, where launching a program will bleed between 600KB and 1MB of memory as shown in the windows task manager. We call the program in a thread and destroy all bitmaps/fonts/activex controls when we're exiting the program. When I look at the debugger's -u output, I can see that the Program memory is staying constant, the file memory is constant, but the Windows and Overhead memory buckets are constantly increasing each time I call the program. Is there any way for me to see what is in these buckets or to tell why they are increasing and not falling back when I exit the program? There are 9 ActiveX controls in total on the window, and some bitmap buttons, I'm assuming destroying them when exiting should release their memory. As this program is run in a thread that we're not waiting for, there is not a cancel that's run after the call, but we do run a Cancel All prior to calling the program, which should free up any memory used by inactive programs. Any assistance troubleshooting this would be of great help.