FIX: _com_ptr_t::operator=(const _variant_t&) AddRefs TwiceLast reviewed: December 18, 1997Article ID: Q168079 |
The information in this article applies to:
SYMPTOMSWhen you use an instantiation of the _com_ptr_t template class and assign a _variant_t to it, the associated COM object may not be released when it should be.
CAUSE_com_ptr_t::operator=(const _variant_t&) calls another member function, QueryStdInterfaces, which ultimately AddRef's upon success. The problem is that operator= also AddRef's upon success.
RESOLUTIONCall Release() explicitly before the object goes out of scope.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in Visual Studio 97 Service Pack 1. For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q170365 TITLE : INFO: Visual Studio 97 Service Packs - What, Where, and Why MORE INFORMATIONThe sample code below demonstrates the problem with operator=(const _variant_t&) of the class template _com_ptr_t. The parameter vt is an IUnknown*. To offset the result of the second AddRef, you need to call punk- >Release before leaving the function below.
Sample Code
// Compile options needed: none // Make an IUnknownPtr _COM_SMARTPTR_TYPEDEF( IUnknown, __uuidof(IUnknown)); void f( const _variant_t & vt ) { IUnknownPtr punk; punk = vt; } Keywords : vcbuglist500 VS97FixlistSP3 kbcode VS97FixlistSP2 VS97FixlistSP1 Version : 5.0 Platform : NT WINDOWS Issue type : kbbug Solution Type : kbfix kbservicepack |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |