Re: [Vala] Help with Memory Leak

[Bruce Reidenbach <bereiden gmail com>]

As they like to say, "old thread is old".

I never was able to get a satisfactory answer from the gtk-app-devel list,
the only response being that the memory allocation/destruction model for
gtk was considered good enough.

But then something curious happened.  I compiled the code for the latest
Ubuntu (13.04) and the problem went away!  The memory footprint is solid as
a rock, after several days of running.  I know there's way too many
variables to figure out what happened (new kernal, new gtk, new valac), but
it appears the problem somehow was cured.  I really doubt that the new
version of valac had anything to do with it since previously I could cause
the heap fragmentation to disappear if I commented out the command to
update the menu label.

On Tue, Jul 17, 2012 at 7:18 AM, Bruce Reidenbach <bereiden gmail com>wrote:

> It undoubtedly is (thanks for the link, BTW).  I have submitted a question
> on the gtk-app-devel mailing list to see if anyone over there has any
> advice on what could be done about heap fragmentation.  I will provide an
> update over here when I have an answer, since I think it might be a good
> thing to have a small footprint for an indicator application.
>
> Thanks to everyone for helping me with this.
>
> Bruce
>
>
> On Mon, Jul 16, 2012 at 8:50 PM, Nor Jaidi Tuah <norjaidi tuah ubd edu bn>wrote:
>
> > > The problem with this code is that the actual labels on the menu did not
> > > update.  I then added the following line to inform the menu entries of a
> > > change:
> > >
> > >     radioItem [item].notify_property ("label");
> > > >
> > >
> > > and the heap size began its slow but steady increase again.
> >
> > Perhaps it is the glib "memory leak".
> >
> > http://developer.gnome.org/gtk-faq/stable/x702.html
> >
> > hand
> > Nor Jaidi Tuah
> >
> >
> > _______________________________________________
> > vala-list mailing list
> > vala-list gnome org
> > https://mail.gnome.org/mailman/listinfo/vala-list