Thread: leaked memory not freed after process is killed?

Another option is to use Electric Fence (gcc prog.c -lefence) to also diagnose mis-use of allocated memory.

You could also try Valgrind. I find it works very well. The thing with Valgrind is that it's basically an entire virtual machine: no instructions are executed directly, Valgrind handles everything. So it lets you detect memory leaks in external libraries and everything. You don't even have to re-compile your program; you don't even need the source for a program to use Valgrind on it.

Of course, I've never used Electric Fence or any other memory leak detection tools besides Valgrind.

In a previous post by the thread-starter:

i've actually been using valgrind to get an indication of what's going on since the application is rather big...

--
Mats