After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 150803 - Console warnings on tab switching
Console warnings on tab switching
Status: RESOLVED FIXED
Product: galeon
Classification: Deprecated
Component: general
1.3.17
Other Linux
: Normal normal
: 1.3.18
Assigned To: galeon-maint
galeon-maint
Depends on:
Blocks:
 
 
Reported: 2004-08-22 23:02 UTC by Thomas Zajic
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
check for group != NULL (372 bytes, patch)
2004-08-23 17:52 UTC, Tommi Komulainen
none Details | Review

Description Thomas Zajic 2004-08-22 23:02:41 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.
Comment 1 Tommi Komulainen 2004-08-23 05:18:35 UTC
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.
Comment 2 Thomas Zajic 2004-08-23 06:41:00 UTC
Done - here's the bug-buddy backtrace:

Backtrace was generated from '/usr/local/bin/galeon'

0x40fba089 in wait4 () from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    from /usr/local/lib/libgnomeui-2.so.0
  • #4 nsProfileLock::FatalSignalHandler
    from /usr/local/lib/mozilla-1.7.2/libgtkembedmoz.so
  • #5 pthread_kill
    from /lib/libpthread.so.0
  • #6 sigaction
    from /lib/libc.so.6
  • #7 raise
    from /lib/libpthread.so.0
  • #8 abort
    from /lib/libc.so.6
  • #9 g_logv
    from /usr/local/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/local/lib/libglib-2.0.so.0
  • #11 g_type_check_instance
    from /usr/local/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/local/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/local/lib/libgobject-2.0.so.0
  • #14 _gtk_action_group_emit_disconnect_proxy
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #15 disconnect_proxy
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #16 disconnect_proxy
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #17 gtk_action_connect_proxy
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #18 update_node
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #19 update_node
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #20 update_node
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #21 update_node
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #22 update_node
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #23 update_node
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #24 do_updates
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #25 gtk_ui_manager_ensure_update
    from /usr/local/lib/libgtk-x11-2.0.so.0
  • #26 galeon_css_menu_rebuild
    at galeon-css-menu.c line 286
  • #27 galeon_css_menu_rebuild_timeout_cb
    at galeon-css-menu.c line 298
  • #28 g_timeout_dispatch
    from /usr/local/lib/libglib-2.0.so.0
  • #29 g_main_dispatch
    from /usr/local/lib/libglib-2.0.so.0
  • #30 g_main_context_dispatch
    from /usr/local/lib/libglib-2.0.so.0
  • #31 g_main_context_iterate
    from /usr/local/lib/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /usr/local/lib/libglib-2.0.so.0
  • #33 bonobo_main
    from /usr/local/lib/libbonobo-2.so.0
  • #34 main
    at galeon-main.c line 197
  • #35 __libc_start_main
    from /lib/libc.so.6

Comment 3 Tommi Komulainen 2004-08-23 16:51:14 UTC
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.
Comment 4 Tommi Komulainen 2004-08-23 17:11:08 UTC
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 ?? ()

Thread 1 (Thread 1088593792 (LWP 18868))

  • #0 ??
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #2 nsProfileLock::FatalSignalHandler(int)
    from /usr/lib/mozilla-1.7.2/libgtkembedmoz.so
  • #3 <signal handler called>
  • #4 ??
  • #5 abort
    from /lib/tls/libc.so.6
  • #6 g_logv
  • #7 g_log
  • #8 g_type_check_instance
    at gtype.c line 3229
  • #9 g_signal_emit_valist
    at gsignal.c line 2121
  • #10 g_signal_emit
    at gsignal.c line 2238
  • #11 _gtk_action_group_emit_disconnect_proxy
    at gtkactiongroup.c line 1110
  • #12 disconnect_proxy
    at gtkaction.c line 954
  • #13 disconnect_proxy
    at gtktoggleaction.c line 298
  • #14 gtk_action_connect_proxy
    at gtkaction.c line 1096
  • #15 update_node
    at gtkuimanager.c line 2371
  • #16 update_node
    at gtkuimanager.c line 2512
  • #17 update_node
    at gtkuimanager.c line 2512
  • #18 update_node
    at gtkuimanager.c line 2512
  • #19 update_node
    at gtkuimanager.c line 2512
  • #20 update_node
    at gtkuimanager.c line 2512
  • #21 do_updates
    at gtkuimanager.c line 2552
  • #22 galeon_css_menu_rebuild
    at ../../src/galeon-css-menu.c line 286
  • #23 galeon_css_menu_rebuild_timeout_cb
    at ../../src/galeon-css-menu.c line 298
  • #24 g_timeout_dispatch
    at gmain.c line 3301
  • #25 g_main_dispatch
    at gmain.c line 1942
  • #26 g_main_context_dispatch
    at gmain.c line 2492
  • #27 g_main_context_iterate
    at gmain.c line 2573
  • #28 g_main_loop_run
    at gmain.c line 2777
  • #29 bonobo_main
    at bonobo-main.c line 297
  • #30 main
    at ../../src/galeon-main.c line 197
  • #31 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??

Comment 5 Tommi Komulainen 2004-08-23 17:52:18 UTC
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.
Comment 6 Crispin Flowerday (not receiving bugmail) 2004-08-23 19:04:46 UTC
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