Maybe try valgrind... But after testing it on a few basic utilities like ls, find xclock, it seems that many of them do have leaks... JD _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: gigantic memory leak in Clock Applet...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: gigantic memory leak in Clock Applet...
- From: John Doe <jdmls@xxxxxxxxx>
- Date: Tue, 8 Jan 2013 06:45:32 -0800 (PST)
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <50EC1E43.9070101@xplanation.com>
- Follow-Ups:
- Re: gigantic memory leak in Clock Applet...
- From: m . roth
- Re: gigantic memory leak in Clock Applet...
- References:
- gigantic memory leak in Clock Applet...
- From: fred smith
- Re: gigantic memory leak in Clock Applet...
- From: ken
- Re: gigantic memory leak in Clock Applet...
- From: fred smith
- Re: gigantic memory leak in Clock Applet...
- From: ken
- Re: gigantic memory leak in Clock Applet...
- From: fred smith
- Re: gigantic memory leak in Clock Applet...
- From: Paul Bijnens
- gigantic memory leak in Clock Applet...
- Prev by Date: Re: sysctl -p at startup?
- Next by Date: Re: gigantic memory leak in Clock Applet...
- Previous by thread: Re: gigantic memory leak in Clock Applet...
- Next by thread: Re: gigantic memory leak in Clock Applet...
- Index(es):
 |