GNOME Bugzilla – Bug 679291
GtkTreeView: cursor-changed signal should not be emitted during destroy cycle
Last modified: 2015-08-13 10:12:23 UTC
Created attachment 217892 [details] Don't emit "cursor-changed" during destroy cycle Bug is present in GTK+ 3.4.3. Brief call stack: gtk_tree_view_destroy() calls gtk_tree_view_set_model(), which calls gtk_tree_view_real_set_cursor(), which emits the "cursor-changed" signal on the GtkTreeView. This leads to unexpected situations for handlers installed on the "cursor-changed" signal, such as gtk_tree_view_get_selection() returning NULL. The attached patch checks gtk_widget_in_destruction() before emitting the "cursor-changed" signal. Originally reported as http://redmine.audacious-media-player.org/issues/141.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 671939 ***
*** Bug 684715 has been marked as a duplicate of this bug. ***