Hi, I've been trying to find mem leaks with Visual Leak Detector. And a few detected on the STL like the example below:
The callstack is:
My leaking code:c:\program files\microsoft visual studio 8\vc\include\xmemory (44): std::_Allocate<char>
c:\program files\microsoft visual studio 8\vc\include\xmemory (146): std::allocator<char>::allocate
c:\program files\microsoft visual studio 8\vc\include\xstring (1972): std::basic_string<char,std::char_traits<char>,std: :allocator<char> >::_Copy
c:\program files\microsoft visual studio 8\vc\include\xstring (2002): std::basic_string<char,std::char_traits<char>,std: :allocator<char> >::_Grow
c:\program files\microsoft visual studio 8\vc\include\xstring (1022): std::basic_string<char,std::char_traits<char>,std: :allocator<char> >::assign
c:\program files\microsoft visual studio 8\vc\include\xstring (1033): std::basic_string<char,std::char_traits<char>,std: :allocator<char> >::assign
c:\program files\microsoft visual studio 8\vc\include\xstring (634): std::basic_string<char,std::char_traits<char>,std: :allocator<char> >::basic_string<char,std::char_traits<char>,std::a llocator<char> >
So you see, it was only some instances of std::string but VLD reported them leaking. Is it really leaking? FYI I'm using then default STL from VS 2005 so if it's leaking, does that mean I should use stlport instead?Code:class DecoFrame { private: std::string m_strOverlayFilename; std::string m_strThumbnailFilename; ... }; DecoFrame::DecoFrame( const char* szOverlayFilename, const char* szThumbnailFilename ) : m_strOverlayFilename( szOverlayFilename ), <-- this one is leaking m_strThumbnailFilename( szThumbnailFilename ), <-- also this one m_pTextureOverlay( NULL ), m_pTextureThumbnail( NULL ) { }



LinkBack URL
About LinkBacks


