Re: memory leak in CComCreator::CreateInstance?

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.win32.programmer.messaging,microsoft.public.vc.atl,microsoft.public.vc.mfc,microsoft.public.vc.mfcole

Date:

Mon, 5 Mar 2007 19:20:48 -0500

Message-ID:

<OmdAMV4XHHA.2556@TK2MSFTNGP02.phx.gbl>

Eric <bauersachs@kull.ch.cuthere.nospam.me.com> wrote:

Detected memory leaks!
Dumping objects ->
{115} normal block at 0x00DBA8A8, 68 bytes long.

When breaking at allocation 115 which causes the problem, I've got the
following call stack (top to bottom):
...
my.exe!AfxInternalPumpMessage()
user32.dll, ole32.dll, rpcrt4.dll, etc.
my.exe!ATL::CComClassFactory::CreateInstance() (line 3299 in atlcom.h
on hRes=m_pfnCreateInstance(pUnkOuter,riid,ppvObj);)
my.exe!ATL::CComCreator2<>::CreateInstance() (line 1880 in atlcom.h on
T2::CreateIntance(pv,riid,ppv);)
my.exe!ATL::CComCreator<>::CreateIntance() (line 1799 in atlcom.h on
ATLTRY(p=new T1(pv)))
my.exe!operator new

This means that a COM object created at this point was never deleted.
That, in turn, most likely means that you have reference counting
problem somewhere. See _ATL_DEBUG_INTERFACES and other ATL debugging
facilities.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925