Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m trying to track down a memory leak in a COM object, and I’m not seeing anything obviously wrong. I’m probably using some of the COM wrappers incorrectly, but my standard toolkit of finding memory leaks (AQtime) isn’t helping me with COM. Does anyone have any tricks/tools to track down COM memory/reference leaks?
If you’re using ATL you can define _ATL_DEBUG_INTERFACES (see MSDN entry). This will certainly help you to catch any leaked interfaces, although obviously it won’t help to catch any resources leaked internally within the object.