I think it's worth pointing out that these normally harmless leaks would
become a problem if gtk was repeatedly loaded and unloaded with
dlopen()+dlclose(). Each dlopen() results in a fresh state, so Gtk would
allocate new instances of these global structures each time.
Not exactly a prominent use case though.
On 9 February 2011 16:50, Michael Torrie <torr...@gmail.com> wrote:
> On 02/09/2011 02:29 PM, John Emmas wrote:
> > But my original example looked like this:-
> >
> >
> > Gtk::Main *app = new Gtk::Main (&argc, &argv);
> >
> > delete app;
>
> Change it to this and then look at memory use:
>
> for (;;) {
> Gtk::Main *app = new Gtk::Main (&argc, &argv);
> delete app;
> }
>
> If memory usage grows then GTK leaks. If it doesn't, there is no leak.
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
>
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
