Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

Catching Memory Leaks

0.00/5 (No votes)
4 Oct 2000 1  
How catch memory leaks with very little effort

Introduction

I would like share with you some experience in catching memory leaks. In most cases, it is a long process and required additional tools like PurifyNT or BoundsChecker. Actually, catching simple memory leaks is possible by using the Microsoft exported functionality.

In a simple case, you should add several lines to 'StdAfx.h':

#ifdef _DEBUG
   #define _CRTDBG_MAP_ALLOC // include Microsoft memory leak detection procedures
   #define _INC_MALLOC	     // exclude standard memory alloc procedures
#endif

Note: It should be before the 'include' directives.

In the enclosed example, you will find an example with a memory leak. To see how it works, you should run program under the debugger. When the program finishes, you will see in the 'Output' window, 'Debug' tab the following message.

Detected memory leaks!
Dumping objects -> D:\Projects\CrtDbg\CrtDbg.cpp(25) : {53} normal block at 0x002F26C0, 10 bytes long.
Data: <MemoryLeak> <MEMORYLEAK> 4D 65 6D 6F 72 79 4C 65 61 6B 
Object dump complete.

In more advanced memory management cases, you should look in the 'AfxMem.cpp' file in MFC source directory. File contents plenty of memory management functions.

I have written a class CMemDiff that wraps CMemoryState and helps track memory leaks. Just include the MemDiff files in your project. A global variable of type CMemDiff is declared and its constructor and destructor will check the state of your memory at the start and end of your program and report any leaks.

License

This article has no explicit license attached to it, but may contain usage terms in the article text or the download files themselves. If in doubt, please contact the author via the discussion board below.

A list of licenses authors might use can be found here.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here