Description of problem: Gmail is very crashy in 2.6.0.... Version-Release number of selected component: webkitgtk4-2.6.0-2.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 31 crash_function: setAtkStateSetFromCoreObject executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess kernel: 3.17.0-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 setAtkStateSetFromCoreObject at /usr/src/debug/webkitgtk-2.6.0/Source/WebCore/accessibility/atk/WebKitAccessibleWrapperAtk.cpp:814 #1 webkitAccessibleRefStateSet at /usr/src/debug/webkitgtk-2.6.0/Source/WebCore/accessibility/atk/WebKitAccessibleWrapperAtk.cpp:940 #2 signal_is_needed at event.c:411 #3 emit_event at event.c:497 #4 children_changed_event_listener at event.c:1096 #7 g_signal_emit_by_name at gsignal.c:3405 #8 WebCore::AXObjectCache::getOrCreate at /usr/src/debug/webkitgtk-2.6.0/Source/WebCore/accessibility/AXObjectCache.cpp:364 #9 WebCore::AccessibilityObject::isARIAHidden at /usr/src/debug/webkitgtk-2.6.0/Source/WebCore/accessibility/AccessibilityObject.cpp:2408 #10 WebCore::AccessibilityObject::defaultObjectInclusion at /usr/src/debug/webkitgtk-2.6.0/Source/WebCore/accessibility/AccessibilityObject.cpp:2429 #11 WebCore::AccessibilityObject::accessibilityIsIgnoredByDefault at /usr/src/debug/webkitgtk-2.6.0/Source/WebCore/accessibility/AccessibilityObject.cpp:2401
Created attachment 946202 [details] File: backtrace
Created attachment 946203 [details] File: cgroup
Created attachment 946204 [details] File: core_backtrace
Created attachment 946205 [details] File: dso_list
Created attachment 946206 [details] File: environ
Created attachment 946207 [details] File: exploitable
Created attachment 946208 [details] File: limits
Created attachment 946209 [details] File: maps
Created attachment 946210 [details] File: open_fds
Created attachment 946211 [details] File: proc_pid_status
Created attachment 946212 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1170831 ***