Click here to Skip to main content
Click here to Skip to main content

Memory leak finder

, 22 Feb 2012 MIT
Rate this:
Please Sign up or sign in to vote.
Custom memory handler with memory leak reporting and no-mans-land checking. Leaks are reported with call stack of allocation.

Sample Image - Memory_leak_finder.jpg

Introduction

Have you ever had a memory leak? Wished you knew where you allocated it and how? Is your boss cheap and refuses to buy Boundchecker or another debugging tool?

Here is the solution for you. A memory leak detector compiled directly into your code. It reports memory leaks with call stack of the allocation down to a user defined depth.

As an add-on, it does simple checks of the memory before and after the memory block, to track buffer overwrites.

Usage

Include tracealloc.cpp in your project. Define DETECT_LEAKS in the project settings. Compile. Run your application. Memory leaks are reported into your debug output window when the application terminates. Just click the memory leak and the correct file and line will be shown.

You can find further instructions in the source code.

How is it done?

The code overrides operator new and operator delete. For each allocation made, the code allocates extra space for tracking, call stack and no-mans-land. The current call stack is fetched and remembered, finally the code puts the newly allocated block in a linked list and the requested memory is returned.

When a memory block is deleted, the header is found and checked for buffer overwrites. The memory block is then removed from the linked list and deallocated.

When the program terminates, the global memory tracker object is deleted. The destructor traverses the linked list for memory blocks that isn’t deleted (= leaked memory). It then fetches symbol information for the call stacks and dumps the information in the debug console.

Limitations

The code is Microsoft Visual Studio and Win32 specific. It requires a debug build. The code is C++ specific. It handles new/delete but not malloc/free. The code will run slower with leak detection active (roughly at half normal debug build speed).

Finally

I want to thank Zoltan Csizmadia who wrote ExtendedTrace. I have used parts of his code for stack walking and symbol lookups.

I also want to thank the Code Project community. I have found many solutions or pointers in the right direction here. I hope I have given something back with this contribution.

Thank you!

History

February 22, 2012:

  • Inclusion of contributed bug fixes (author acknowledged in read me file)
  • Upgrade of solution to Visual Studio 2010.

License

This article, along with any associated source code and files, is licensed under The MIT License

Share

About the Author

Erik Rydgren
Software Developer (Senior)
Sweden Sweden
B.Sc in Software engineering
 
Writing software for the finance market.
Languages known: C/C++, SQL, Java, Perl, M68000 assembly and more. Give me the syntax and I'll program in it.
 
In my spare time i like to watch movies, read books and play computergames.

Comments and Discussions

 
GeneralTrouble in tracking memory leak PinmemberChandrasekar S10-Oct-05 3:20 
GeneralMissing __cdecl PinmemberJoão Paulo Figueira4-May-05 11:05 
GeneralFixing bugs PinmemberSergey Solozhentsev5-Dec-04 22:03 
GeneralTrouble Getting Leak Details PinsussAColombi5-Nov-04 20:24 
GeneralRe: Trouble Getting Leak Details PinmemberErik Rydgren7-Nov-04 21:30 
GeneralGetLastError() after new PinmemberMisanthrop7-Oct-04 6:48 
GeneralRe: GetLastError() after new PinmemberErik Rydgren8-Oct-04 5:17 
Generalwrong line numbers pointed Pinmemberbnujos29-Sep-04 21:51 
GeneralRe: wrong line numbers pointed PinmemberErik Rydgren29-Sep-04 23:53 
GeneralCompiler error with _UNICODE Pinmemberjpteruel27-Sep-04 23:23 
GeneralRe: Compiler error with _UNICODE PinmemberErik Rydgren28-Sep-04 0:19 
GeneralRe: Compiler error with _UNICODE Pinmemberjpteruel28-Sep-04 0:35 
GeneralRe: Compiler error with _UNICODE PinmemberErik Rydgren28-Sep-04 0:40 
GeneralRe: Compiler error with _UNICODE Pinmemberjpteruel28-Sep-04 3:22 
Generalusing memory leak finder in a project with multiple dlls PinmemberKevin Cao20-Sep-04 21:24 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberErik Rydgren22-Sep-04 4:26 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberDieter Hammer23-Sep-04 6:28 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberErik Rydgren23-Sep-04 6:40 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberCurtis W23-Sep-04 8:25 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberErik Rydgren23-Sep-04 21:27 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberCurtis W23-Sep-04 22:47 
GeneralRe: using memory leak finder in a project with multiple dlls PinsussJaniOrca24-Sep-04 2:36 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberJonas O15-Oct-04 5:34 
GeneralRe: using memory leak finder in a project with multiple dlls PinmemberErik Rydgren15-Oct-04 5:41 
Generalmemory decrease PinsussAnonymous28-Jul-04 18:56 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.141223.1 | Last Updated 22 Feb 2012
Article Copyright 2003 by Erik Rydgren
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid