Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Detecting Memory Leaks

   From: Bob Gorman <bob at>
   Date: Thu, 15 Jul 2004 19:17:14 -0400

   At 04:01 PM 7/15/2004, Samuel Donham wrote:
   >One of my clients claims that I have a memory leak in one of our
   >applications.  He claims that 'top' reports my app is slowly consuming
   >more memory after running for 30 days (now 20 megs, up from 8 when it was
   >first started).  Perhaps there is a memory leak, but I don't think 'top'
   >is a good indicator of one ('free' would be much better).

   You can also try some other display options of 'top', with the F
   (field) command.  You may find these fields of interest:

Valgrind is an excellent tool for this purpose, although it does slow
the application down tremendously.

Robert Krawitz                                     <rlk at>

Tall Clubs International  -- or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lpf at
Project lead for Gimp Print   --

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /