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? Thanks, David
Attachment:
valgrind.tmp
Description: Text document