Version-Release number of selected component: evolution-3.6.4-2.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: WTF::fastFree executable: /usr/bin/evolution kernel: 3.8.3-203.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 WTF::fastFree at /lib64/libjavascriptcoregtk-3.0.so.0 #1 WebCore::SharedBuffer::clear at /lib64/libwebkitgtk-3.0.so.0 #2 WebCore::SharedBuffer::~SharedBuffer at /lib64/libwebkitgtk-3.0.so.0 #3 WebCore::ArchiveResource::~ArchiveResource at /lib64/libwebkitgtk-3.0.so.0 #4 webkit_web_resource_dispose at /lib64/libwebkitgtk-3.0.so.0 #6 webkit_web_view_dispose at /lib64/libwebkitgtk-3.0.so.0 #8 gtk_scrolled_window_forall at gtkscrolledwindow.c:1581 #9 gtk_container_destroy at gtkcontainer.c:1377 #14 gtk_widget_dispose at gtkwidget.c:10270 #16 gtk_box_forall at gtkbox.c:1865
Created attachment 714433 [details] File: backtrace
Created attachment 714434 [details] File: build_ids
Created attachment 714435 [details] File: cgroup
Created attachment 714436 [details] File: core_backtrace
Created attachment 714437 [details] File: dso_list
Created attachment 714438 [details] File: environ
Created attachment 714439 [details] File: limits
Created attachment 714440 [details] File: maps
Created attachment 714441 [details] File: open_fds
Created attachment 714442 [details] File: proc_pid_status
Created attachment 714443 [details] File: smolt_data
Created attachment 714444 [details] File: var_log_messages
Thanks for a bug report. I do not see what could happen here from the backtrace, could you provide any steps for a reproducer, please? The only thing I see from the backtrace is that you were closing a message view which you had opened in a separate window (like after double-click in a message list). Maybe it is related to certain message?
James can you try it with webkitgtk3-2.0.0-1 if the problem still persist?
I'm happy to upgrade to webkitgtk3-2.0.0-1 and see what happens, but I don't have a way of reproducing the crash, so I will not be able to say for certain that it's solved...
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.