On Sun, 2006-08-20 at 05:48 -0400, David Ellis wrote: > Hello, > > Could anyone offer help or advice on debugging mysterious gtk-related memory > leaks and errors reported by valgrind when checking a threaded GTK+ > program? The primary "potential" leak seems to be a sizeable chunk in > g_thread_init, and there are quite a few errors from various unknown > contexts (including g_module_open). > > Please take a look at the attached valgrind --leak-check=full output, > and/or offer general advice on pursuing such errors and leaks, which are > almost undoubtedly caused by my code, yet do not appear to come from any > context I am familiar with. Is there some procedure for cleaning up > g_threads, apart from adding a window "destroy" handler like > gtk_main_quit?
Maybe you should set G_SLICE=always-malloc in the environment in order to make valgrind more useful: http://developer.gnome.org/doc/API/2.0/glib/glib-running.html \David -- _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
