GNOME Bugzilla – Bug 319415
GLib-GObject assertions failing in natively compiled java-gnome code
Last modified: 2008-02-13 01:48:32 UTC
Please describe the problem: When running Frysk (sourceware.org/frysk) after natively compiling it, the following messages are generated: (java-gnome:15536): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (java-gnome:15536): GLib-GObject-CRITICAL **: g_object_remove_toggle_ref: assertion `G_IS_OBJECT (object)' failed I have also gotten NullPointerExceptions, although with far less frequency: Exception in thread "main" java.lang.NullPointerException at .g_type_check_instance_is_a (/opt/frysk/lib/libgobject-2.0.so.0.800.2) at .g_object_get_data (/opt/frysk/lib/libgobject-2.0.so.0.800.2) at .getData (/opt/frysk/lib/libgtkjni-2.8.so) at .processPendingGObject (/opt/frysk/lib/libgtkjni-2.8.so) at .g_main_context_dispatch (/opt/frysk/lib/libglib-2.0.so.0.800.2) at .g_main_loop_run (/opt/frysk/lib/libglib-2.0.so.0.800.2) at .gtk_main (/opt/frysk/lib/libgtk-x11-2.0.so.0.800.4) at .Java_org_gnu_gtk_Gtk_gtk_1main (/opt/frysk/lib/libgtkjni-2.8.so) at org.gnu.gtk.Gtk.gtk_main() (/opt/frysk/lib/libgtkjava-2.8.so) at org.gnu.gtk.Gtk.main() (/opt/frysk/lib/libgtkjava-2.8.so) at frysk.gui.test.SourceWinRunner.mainSourceWin(java.lang.String[], java.lang.String[], java.lang.String) (/home/ajocksch/frysk-install/../../frysk/frysk-gui/frysk/gui/test/SourceWinRunner.java:93) at frysk.bindir.frysk.main(java.lang.String[]) (/home/ajocksch/frysk-install/../../frysk/frysk-gui/frysk/bindir/frysk.java:64) at gnu.java.lang.MainThread.call_main() (/usr/lib/libgcj.so.6.0.0) at gnu.java.lang.MainThread.run() (/usr/lib/libgcj.so.6.0.0) This seems to happen when the source window (run by 'frysk --sourcewin' after a full install) is scrolled. I will try to nail down a better test case. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
I think this bug is related to bug #156442.
Or maybe it isn't related, that one is about ToolBar.setToolTips. This one seems to be caused by the fact that ToolTips#setTip fails to increase the ref_count of the native object so it gets collected before the time (this was established from some investigation based on additional input from Adam).
I had a look at gtk+ code for gtk_tooltips_set_tip. It increases the ref_count of the GtkWidget, but it does not increase the ref_count of the GtkTooltips.
Adam, Is this bug still extant, or did it get polished of along the way somewhere? AfC
AFAIK this bug is still existant. I haven't checked recently to see if the reference count for the GtkTooltips was being incremented within GTK.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.