【发布时间】:2020-11-24 13:52:39
【问题描述】:
我有返回 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 的误报还是我错过了释放字符串的一些内容?
【问题讨论】:
标签: visual-c++ memory-leaks com bstr