2013/1/23 David Nečas <y...@physics.muni.cz> > > Whether gtk_combo_box_get_path_for_child() can be called with a visible > child different from those enumerated there (the only way a leak can > occur) I cannot tell. > > In any case, any suspected leak that goes through GSlice should be first > reproduced with G_SLICE=always-malloc -- and you find it real, a bug > report is much better than suppression... > > I did use G_SLICE=always-malloc. Strange thing is that on another program (rodent-fgr) there is no leak with the creation of combobox with entry. The only difference is that in rodent-fgr, all work is done by the main thread and the combobox is in the main window, while in rodent, the work is invoked from a non-main thread by means of a g_main_context_invoke() and the combobox is in a dialog.
Maybe it's just a bug in Valgrind... I'm finding that a threaded environment may confuse Valgrind. I'll do some more checking. Edscott _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
