GNOME Bugzilla – Bug 138653
crash opening/closing multiple gnome-terminal tabs
Last modified: 2007-01-25 01:01:32 UTC
Using a GNOME build from 29th of March 2004 -From xterm, launched gnome-terminal -Opened 4 or 5 tabs -In one tab, launch 'gnopernicus' -Closed 2 tabs (The steps above are an approximation - narrowing the steps down was difficult) RESULT:gnome-terminal segmentation faulted. Here is the stack trace: ------------------------ Program received signal SIGSEGV, Segmentation fault.
+ Trace 45561
Thread 1024 (LWP 3880)
There are patches in other vte bugs which I would like applied before lookinmg this too closely. It suspect the variable widget has value NULL and is being dereferenced.
I don't get a crash, but each time I close a tab, on stderr I get something similar to: (gnome-terminal:898): GLib-GObject-WARNING **: g_object_weak_unref: couldn't find weak ref 0x40d3e690(0x8271174) (gnome-terminal:898): GLib-GObject-WARNING **: invalid uninstantiatable type `<unknown>' in cast to `AtkObject' (gnome-terminal:898): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `<unknown>' (gnome-terminal:898): GLib-GObject-CRITICAL **: file gsignal.c: line 2122 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Padraig: can you add the bug numbers you wait upon to the blocking list?
Created attachment 27226 [details] [review] Proposed patch I am unable to reproduce this crash but the attached patch should be applied as it prevents an attempt to get accessibility information about a widget which has been destroyed.
Please review and commit if it's ok.
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs. Filter on "SUN A11Y SPAM" to ignore.
Padraig, is this also part of the patch for bug #113590? It looked very similar to some of the hunks in there.
This should be fixed by this commit I guess: 2005-07-07 Matthias Clasen <mclasen@redhat.com> * src/vte.c (vte_terminal_unrealize): Unset the user data on the gdk window.
At some point the proposed patch was applied, possibly as part of bug 113590 and all dependencies have been resolved.