Description of problem: I had 4 open php files all in tabs and waas editing the user preferences and bluefish crashed. See https://bugzilla.redhat.com/show_bug.cgi?id=929347 and https://bugzilla.redhat.com/show_bug.cgi?id=1027404 Reproducible: Always Actual Results: Version-Release number of selected component: bluefish-2.2.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: /bin/bluefish /home/Build/etc/osca/osca.conf crash_function: Oxygen::WidgetLookup::find executable: /usr/bin/bluefish kernel: 3.8.4-202.fc18.x86_64 uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 Oxygen::WidgetLookup::find at /usr/src/debug/oxygen-gtk3-1.1.2/src/oxygenwidgetlookup.cpp:110 #1 Oxygen::render_background at /usr/src/debug/oxygen-gtk3-1.1.2/src/oxygenthemingengine.cpp:212 #2 gtk_render_background at gtkstylecontext.c:3791 #3 _gtk_text_handle_draw at gtktexthandle.c:118 #4 _gtk_text_handle_update_shape at gtktexthandle.c:143 #5 _gtk_text_handle_create_window at gtktexthandle.c:197 #6 _gtk_text_handle_update_window at gtktexthandle.c:304 #7 _gtk_text_handle_update_windows at gtktexthandle.c:320 #12 _gtk_widget_style_context_invalidated at gtkwidget.c:13973 #17 gtk_style_context_do_invalidate at gtkstylecontext.c:3004 Te same with oxygen-gtk3-1.2.0 Truncated backtrace: Thread no. 1 (10 frames) #0 Oxygen::WidgetLookup::find at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenwidgetlookup.cpp:110 #2 Oxygen::render_background at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenthemingengine.cpp:212 #3 gtk_render_background at gtkstylecontext.c:3908 #4 _gtk_text_handle_draw at gtktexthandle.c:130 #5 _gtk_text_handle_update_shape at gtktexthandle.c:156 #6 _gtk_text_handle_create_window at gtktexthandle.c:219 #7 _gtk_text_handle_set_relative_to at gtktexthandle.c:594 #8 gtk_entry_realize at gtkentry.c:3161 #13 gtk_widget_realize at gtkwidget.c:4824 #14 gtk_widget_map at gtkwidget.c:4359
happens every time, really ? The backtrace looks like a case of widget deletion that is not caught by our code. Meaning that the "destroy" signal was not either sent or recieved. Can be memory corruption or something more profound (but then I'd expect pretty much all applications to crash)
I don't know is it every time crashes.
Can't make it crash here, same version.
> I was editing my user preferences when the crash happen. https://bugzilla.redhat.com/show_bug.cgi?id=929347#c12
*** Bug 328681 has been marked as a duplicate of this bug. ***
Twice the exact same crash with different applications. I have same oxygen-gtk3, same glib gtk3 is version 3.10.6 Can someone try to upgrade ?
In Fedora 19 gtk3 version 3.8.8.
Well, still that's the same crash ... Can't fix if I can't reproduce, though ... (the crash seems to be due to some widget being invalid, which should not happen provided that we get the "destroy" signal) also, the same method is used everywhere, and for every single rendering call. So no easy bug there (otherwise all would crash, immediately).
ok. Good news. I can reproduce a similar crash here on another system, though with quite older gtk3 version (3.6.x) Happens with pretty much any application that has a spinbox. I'll investigate further.
Closing, since the "duplicated" bug #328681 was fixed. (assuming the issue is the same, which is very likely) Feel free to re-open if crash still happens with oxygen-gtk3-1.3.1 or above. I also backported the fix to oxygen-gtk3-1.2, but this will need a new release (for older gtk3 versions, < 3.9)