[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: mem leaks in file_selection widget for gtk 2.x
- From: Ed Sweetman <ed sweetman wmich edu>
- To: Havoc Pennington <hp redhat com>
- Cc: gtk-app-devel-list <gtk-app-devel-list gnome org>
- Subject: Re: mem leaks in file_selection widget for gtk 2.x
- Date: 22 Mar 2002 19:04:44 -0500
It doesn't seem to be a literal leak. But the program uses more and
more memory instead of freeing it like it did in gtk 1.2. When i push
the leak button i have a very small amount colored red and that portion
hardly changes as the actual memory use increases indefinitely with gtk
2.x. I call it a leak because the effect is the same and i'm not sure
what besides bloat could describe the effect when compared to gtk1.2.
I was told that memprof has a bug where it incorrectly reports memory
usage for gtk2.x programs because gtk1.2 does not expose the bug. I
found this to be somewhat wrong because i see the same behavior just
looking at ps aux output.
On Fri, 2002-03-22 at 18:43, Havoc Pennington wrote:
>
> Ed Sweetman <ed.sweetman@wmich.edu> writes:
> > In gtk 1.2 I observe this perfectly.
> > In gtk 2.0 (from debian unstable) I see a mem leak because very little
> > memory is freed and much more memory is eaten each selection. I can
> > watch the memory go up as i scroll through directories and I watch the
> > memory release when the file is finished being rendered at a higher
> > level than when it started out at.
>
> Push the "leaks" button in memprof and see where the memory is coming from.
> (Though you may need a GTK built with symbols for that, I guess.)
>
> Havoc
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]