Re: Unified Event Model and support for multithreaded usage
Heres the original post from 5 years ago (the bug originates
in VC 7.0, part of VS.NET 2002):
http://groups.google.com/group/microsoft.public.win32.programmer.ole/browse_thread/thread/547ef1429cfacd36
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Boris" <boris@gtemail.net> wrote in message
news:op.t1uxcpdy45fww6@burk.mshome.net...
On Mon, 12 Nov 2007 22:56:24 +0100, Alexander Nickolov
<agnickolov@mvps.org> wrote:
No, it's not this, and BTW, what kind of events did you expect in
ATL anyway? ATL has nothing to do with .NET - it's all native.
I was referring to Microsoft's distinction between COM events and native
events (native as events in standard C++ without COM).
The problem I'm talking about was with dispinterfaces and
mishandining the EXCEPINFO argument to IDispatch::Invoke
which ends up being leaked. E..g we are talking about __raise.
Do you have a link where I can read more about this memory leak? As I'm
not working on a commercial software but on a proof of concept I'm not
bothered too much for now. If there is a way to fix it easily I'd like to
hear though.
Boris