GNOME Bugzilla – Bug 150803
Console warnings on tab switching
Last modified: 2004-12-22 21:47:04 UTC
Environment: Galeon-1.3.17, Mozilla-1.7.2 (GTK+2), GNOME-2.6 (not actually running a GNOME session, though), everything self-compiled, on a Slackware-8.1 system. With several tabs open, Galeon eventually starts printing the following error messages to the console when switching back and forth between tabs: [zlatko@disclosure]:~$ galeon (galeon:28199): GLib-GObject-WARNING **: invalid (NULL) pointer instance (galeon:28199): GLib-GObject-CRITICAL **: file gsignal.c: line 2121 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (galeon:28199): Gtk-WARNING **: GaleonCSSNoneActionItem: missing action (galeon:28199): GLib-GObject-WARNING **: invalid (NULL) pointer instance (galeon:28199): GLib-GObject-CRITICAL **: file gsignal.c: line 2121 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (galeon:28199): GLib-GObject-WARNING **: invalid (NULL) pointer instance (galeon:28199): GLib-GObject-CRITICAL **: file gsignal.c: line 2121 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (galeon:28199): GLib-GObject-WARNING **: invalid (NULL) pointer instance (galeon:28199): GLib-GObject-CRITICAL **: file gsignal.c: line 2121 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (galeon:28199): GLib-GObject-WARNING **: invalid (NULL) pointer instance (galeon:28199): GLib-GObject-CRITICAL **: file gsignal.c: line 2121 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (galeon:28199): Gtk-WARNING **: GaleonCSSNoneActionItem: missing action [zlatko@disclosure]:~$ In this case, I've had the following URLs opened in tabs (from left to right): http://unix.freshmeat.net/daily/2004/08/22/ http://xpenguins.seul.org/ http://icculus.org/~ravage/mohaa/ http://galeon.sourceforge.net/Main/GaleonDevelopment http://bugzilla.gnome.org/show_bug.cgi?id=132381 http://www.spamcop.net/ As I'm rather sensitive to bugs in Galeon's tab handling (see the a.m. bugzilla.gnome.org URL ;-), I thought I'd report this. I already have a debug build ready (CFLAGS=-g CXXFLAGS=-g ./configure), but I'm not sure what to do with it (Galeon doesn't actually crash, so I don't know how to get a proper backtrace - yup, I'm not a gdb wizard). One thing that I did notice with the debug build, though, is that the "GaleonCSSNoneActionItem: missing action" lines are _not_ printed, only the "invalid (NULL) pointer instance" and "assertion `G_TYPE_CHECK_INSTANCE (instance)' failed" lines. I have no idea whether this is actually meaningful or just pure coincidence.
Someone mentioned the javascript related crash might have resurfaced, this could be it but I'm not certain. You can run galeon with '--g-fatal-warnings' command line option and it will abort on the first WARNING message. After that bug-buddy (or gdb if run in it manually) can get the backtrace.
Done - here's the bug-buddy backtrace: Backtrace was generated from '/usr/local/bin/galeon' 0x40fba089 in wait4 () from /lib/libc.so.6
+ Trace 49556
Hmm, well, I can reproduce this by opening the mentioned URLs and switching between tabs quickly for a while with Alt+<number> .. I'm guessing something funny happens with the timeout.
More debugging symbols: Backtrace was generated from '/opt/gnome/bin/galeon' [New Thread 1088593792 (LWP 18868)] [New Thread 1119738672 (LWP 18879)] [New Thread 1107131184 (LWP 18870)] 0xffffe002 in ?? ()
+ Trace 49573
Thread 1 (Thread 1088593792 (LWP 18868))
Created attachment 30866 [details] [review] check for group != NULL This patch against gtk+ gets rid of most of the warnings, but the 'missing action' one still persists.
Thanks very much for the bug report. I have fixed the real problem in CVS, which was a collision of action names: http://lists.gnome.org/archives/cvs-commits-list/2004-August/msg06144.html