Using GTK 2.2.4, we are getting a segmentation fault in
g_object_run_dispose called from gtk_widget_destroy on a fixed container.
The context is a screen that works fine when operated on slowly, such that
all widgets are displayed before any action is taken. The problem only
occurs if you "type ahead" a button press via a keyboard accelerator which
causes the not-yet-actually-displayed widgets to be deleted so that they
can be recreated with new data. Here is the debugger breakdown of the
offending fixed container widget at this point. It looks like it was not
fully created. In particular ref_count is garbage and several of the
other fields have null values.
m_pGTKFixedContainer=0x8f9e58
public
object
private_flags=61580
state=.
saved_state=.
name=0x0
style=0x0
requisition
public
width=0
height=0
allocation
public
x=0
y=0
width=0
height=0
window=0x7a9514
public
parent_instance
public
g_type_instance
ref_count=7975624
qdata=0x0
parent=0x0
What could cause this? Is it necessary to test the widget in some way to
make sure it was fully created before calling gtk_widget_destroy on it?
Or is there a different way of destroying it that would not cause the
problem here?
Sincerely,
John Boncek
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
