Boost C++ Libraries: Ticket #5582: There is a memory leak in the BOOST_AUTO_TEST_CASE_TEMPLATE

attachment set

Mon, 30 May 2011 15:09:04 GMT

attachment → BoostTestMemoryLeak.zip

Configured VS2008 test application which reproduces the memory leak in boost::test library

harningt@… — Mon, 25 Jul 2011 15:47:23 GMT

Any status change on this? If there is a workaround that I can put in place to alleviate this problem before it is put in a release, that would be great.

Tue, 16 Aug 2011 07:55:53 GMT

It seems that issue is not in boost test library, but with memory leaks detection itself. The leak detected is a memory allocated for type_info (typeid) but not yet freed.

Here is the MSDN page related to the issue: http://connect.microsoft.com/VisualStudio/feedback/details/106937/memory-leaks-reported-by-debug-crt-inside-typeinfo-name

Here is the smallest code that reproduces the "leak":

#include <crtdbg.h>
#include <typeinfo> // for typeid
int main()
{
   _CrtSetReportMode(_CRT_WARN, _CRTDBG_MODE_FILE);
   _CrtSetReportFile(_CRT_WARN, _CRTDBG_FILE_STDOUT);
   _CrtSetDbgFlag(_CrtSetDbgFlag( _CRTDBG_REPORT_FLAG ) | _CRTDBG_LEAK_CHECK_DF);
   typeid(int).name();
   return 0;
}

The good news here is that there is a workaround for this issue provided on the MSDN page specified above. Minimum code that worked in my case is:

void free_typeinfo_memory()
{
   __type_info_node *pNode = __type_info_root_node.next;
   __type_info_node *tmpNode = &__type_info_root_node;
   for( ; pNode!=NULL; pNode = tmpNode )
   {
      tmpNode = pNode->next;
      delete pNode->memPtr;
      delete pNode;
   }
}

I have placed the call to free_typeinfo_memory() at the very last line of the main() and leaks didn't come up again :)

status changed; resolution set

Gennadiy Rozental — Sun, 16 Oct 2011 05:12:03 GMT

status new → closed
resolution → fixed

(In [74958]) Introduces notion of framework shutdown Fixes #5582

milestone changed

Raffi Enficiaud — Tue, 07 Jul 2015 08:23:45 GMT

milestone Boost 1.47.0 → Boost 1.59.0