当返回BSTR时,MemoryLeak或DeLeaker的假阳性



我有一个返回BSTR的COM函数。它是这样使用的:

接口:

interface ITexts : IDispatch
{
[id(5)] HRESULT GetText([in] long Number, [in] long LangID, [out,retval] BSTR* pText);
};

的实施

STDMETHODIMP CTexts::GetText(long Number, long LangID, BSTR *pText)
{
CString sDummyValue = _T("gettext"); //just for testing
sDummyValue.SetSysString(pText);
return S_OK;
}

以及客户端

CString RITexts::GetText(long Number, long LangID)
{
CString result;
static BYTE parms[] = VTS_I4 VTS_I4;
InvokeHelper(0x5, DISPATCH_METHOD, VT_BSTR, (void*)&result, parms, Number, LangID);
return result;
}

当以调试版本运行时,Visual Studio不会抱怨,但DeLeaker(一种内存泄漏监测工具(认为存在内存泄漏:

OLEAUT32.dll!SysReAllocStringLen 76543120
mfc140ud.dll!ATL::ChTraitsCRT<wchar_t>::ReAllocSysString Line 815 + 0xe bytes 7a2d0012
mfc140ud.dll!ATL::CStringT<wchar_t,StrTraitMFC_DLL<wchar_t,ATL::ChTraitsCRT<wchar_t> > >::SetSysString Line 2288 + 0x16 bytes 7a2d0a39
(-> ComClass) LangSupp.dll!CTexts::GetText Line 343 + 0x9 bytes 7b1698b2
OLEAUT32.dll!DispCallFunc + 0x16d bytes 7655840d
OLEAUT32.dll!CTypeInfo2::Invoke + 0x2e6 bytes 7653aca6
LangSupp.dll!ATL::CComTypeInfoHolder::Invoke Line 4204 + 0x31 bytes 7b15c056
LangSupp.dll!ATL::IDispatchImpl<ITexts,&IID_ITexts,&LIBID_LANGSUPPLib,1,0,ATL::CComTypeInfoHolder>::Invoke Line 5163 + 0x2a bytes 7b15bfa2
mfc140ud.dll!COleDispatchDriver::InvokeHelperV Line 399 + 0x7 bytes 7a1e6d6b
mfc140ud.dll!COleDispatchDriver::InvokeHelper Line 554 + 0x1d bytes 7a1e6597
(-> Client) Managers.dll!RITexts::GetText Line 104 + 0x1b bytes 7ac2ce3a 

那么,这是DeLeaker的假阳性,还是我错过了释放字符串的一些内容?

服务器是正确的,客户端是错误的。您希望使用变体类型从自动化调用中获取结果。尝试:

CString RITexts::GetText(long Number, long LangID)
{
static BYTE parms[] = VTS_I4 VTS_I4;
_variant_t vResult;
InvokeHelper(0x5, DISPATCH_METHOD, VT_VARIANT, (void*)&vResult, parms, Number, LangID);
CString result((wchar_t*) vResult.bstrVal); // should have error checking of your result and type
return result;
}

调用InvokeHelper不正确。

result的类型应该是BSTR,或者更好的是使用像_bstr_t或CComBSTR这样的包装器来确保为BSTR分配的内存将被释放。

最新更新