dasher (together with X, that starts doing the same few moments after having launched dasher) consumes all the cpu. It doesn't seem to freeze but runs *very* slowly being unusable. Reproducible: Always Steps to Reproduce: 1. emerge dasher 2. run dasher Actual Results: A list of returned assertion errors follow: (dasher:23909): Gtk-CRITICAL **: file gtkwidget.c: line 2219 (gtk_widget_realize): assertion `GTK_IS_WIDGET (widget)' failed (dasher:23909): Gtk-CRITICAL **: file gtktreeview.c: line 8637 (gtk_tree_view_set_model): assertion `GTK_IS_TREE_VIEW (tree_view)' failed (dasher:23909): Gtk-CRITICAL **: file gtktreeview.c: line 8785 (gtk_tree_view_get_selection): assertion `GTK_IS_TREE_VIEW (tree_view)' failed (dasher:23909): Gtk-CRITICAL **: file gtktreeselection.c: line 191 (gtk_tree_selection_set_mode): assertion `GTK_IS_TREE_SELECTION (selection)' failed (dasher:23909): Gtk-CRITICAL **: file gtktreeview.c: line 9071 (gtk_tree_view_append_column): assertion `GTK_IS_TREE_VIEW (tree_view)' failed (dasher:23909): GLib-GObject-WARNING **: invalid (NULL) pointer instance (dasher:23909): GLib-GObject-CRITICAL **: file gsignal.c: line 1634 (g_signal_connect_data): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (dasher:23909): Gtk-CRITICAL **: file gtktreeselection.c: line 853 (gtk_tree_selection_select_iter): assertion `GTK_IS_TREE_SELECTION (selection)' failed (dasher:23909): Gtk-CRITICAL **: file gtktreeview.c: line 10574 (gtk_tree_view_set_cursor_on_cell): assertion `GTK_IS_TREE_VIEW (tree_view)' failed
Please provide the output from "emerge info" on your system, and tell us what version of dasher you're dealing with. Thanks.
Created attachment 31131 [details] emerge info output The version of dasher I'm dealing with is 3.2.10
I've committed dasher-3.2.10-r1 with a patch that removes the warnings (and make the colour preferences widget work), but I still can't find the reason for dasher to "burn out" cpu cycles. Therefore, I'm tempted to close this bug as WORKSFORME, unless you can provide a clear way to reproduce this behaviour consistently on any machine. Try troubleshooting it a little more. We need to know the exact cause of this problem.
Not reproducible.
