FIX: Using Run-Time Type Info May Cause Memory Leak Report

MORE INFORMATION

When you call the 'name' member function of the type_info and then later call _CrtDumpMemoryLeaks, memory leaks are incorrectly reported. The following sample code demonstrates the problem.

Sample Code

/* Compile options needed: /D_DEBUG
*/ 

#include <typeinfo.h>
#include <iostream.h>
#include <crtdbg.h>

struct test {};

void main()
{
    test t;
    typeid(t).name();
    _CrtDumpMemoryLeaks();
}
				

You would see messages similar to the following in the debug tab of the output window: NOTE: If you are using the 'name' member function within an MFC application, the leaks will be reported even if you do not explicitly call _CrtDumpMemoryLeaks. MFC calls this function automatically when the application terminates.