G
Guest
Hi:
We have a problem when host a Windowform control in MFC. The logic we used
just as Chris Sells article:
http://msdn.microsoft.com/msdnmag/issues/03/03/WindowsForms/#S4
Everything went good. The control hosted in a MFC dialog. After open/close
the dialog for couple of times, then we have following error:
Managed Debugging Assistant 'ReportAvOnComRelease' has detected a problem in
'v:\Barracuda\Console\Bin\Barracuda.exe'.
Additional Information: An exception was caught but handled while releasing
a COM interface pointer through Marshal.Release or Marshal.ReleaseComObject
or implicitly after the corresponding RuntimeCallableWrapper was garbage
collected. This is the result of a user refcount error or other problem with
a COM object's Release. Make sure refcounts are managed properly. The COM
interface pointer's original vtable pointer was 0x78307604. While these types
of exceptions are caught by the CLR, they can still lead to corruption and
data loss so if possible the issue causing the exception should be addressed
If it happens in the debug, you click the Continue button for couple of
times, it can recovered from the exception.
Anyone have idea what is going on?
Thanks in advance.
We have a problem when host a Windowform control in MFC. The logic we used
just as Chris Sells article:
http://msdn.microsoft.com/msdnmag/issues/03/03/WindowsForms/#S4
Everything went good. The control hosted in a MFC dialog. After open/close
the dialog for couple of times, then we have following error:
Managed Debugging Assistant 'ReportAvOnComRelease' has detected a problem in
'v:\Barracuda\Console\Bin\Barracuda.exe'.
Additional Information: An exception was caught but handled while releasing
a COM interface pointer through Marshal.Release or Marshal.ReleaseComObject
or implicitly after the corresponding RuntimeCallableWrapper was garbage
collected. This is the result of a user refcount error or other problem with
a COM object's Release. Make sure refcounts are managed properly. The COM
interface pointer's original vtable pointer was 0x78307604. While these types
of exceptions are caught by the CLR, they can still lead to corruption and
data loss so if possible the issue causing the exception should be addressed
If it happens in the debug, you click the Continue button for couple of
times, it can recovered from the exception.
Anyone have idea what is going on?
Thanks in advance.