Re: checking for memory leaks in gtk
- From: Aron Rubin <aron rubin lmco com>
- To: Harinandan S <harinandans gmail com>
- Cc: gtk-list gnome org, paul linuxaudiosystems com
- Subject: Re: checking for memory leaks in gtk
- Date: Mon, 12 May 2008 10:11:04 -0400
Not sure if it will work but there is this project:
Harinandan S wrote:
> I looked at memory usage using 'top' and 'free' while running the
> application and found that memory kept on increasing without decreasing
> when i destroyed a window and finally application was terminated by MVL.
> Meanwhile 'valgrind' is not supported on arm-linux platform so i am not
> able to get more details. I'll try to run it on a x86 linux PC with
> On Thu, May 8, 2008 at 6:52 PM, Paul Davis <paul linuxaudiosystems com
> <mailto:paul linuxaudiosystems com>> wrote:
> On Wed, 2008-05-07 at 19:53 +0530, Harinandan S wrote:
> > Hi All,
> > I have observed memory leak in GTK+ too. I have multiple windows
> > created when some buttons are pressed and destroyed later. I observed
> > that when i destroy a window memory allocated to it during its
> > creation is not freed and memory consumed accumulates and application
> > is killed by OS after a few window create and destroy cycles.
> > I am using GTK+ 2.12.2 with MontaVista linux on TI DM6446 platform.
> > Does anyone know why gtk_widget_destroy is not freeing memory?
> You don't know that. In fact, from the first paragraph of what you
> wrote, its not clear to me that you understand the relationship between
> memory allocated by an application using malloc(3) and the operating
> system. How are you concluding that memory allocated for a given object
> is not freed?
> gtk-list mailing list
> gtk-list gnome org
ssh aron rubinium org cat /dev/brain | grep ^work:
Aron Rubin Senior Member, Engineering Staff
Lockheed Martin E-Mail: arubin atl lmco com
Advanced Technology Laboratories Phone: 856.792.9865
3 Executive Campus Fax: 856.792.9930
Cherry Hill, NJ USA 08002 Web: http://www.atl.lmco.com
] [Thread Prev