Description of problem: This issue happens with WebKit rendering mails inside evolution. It is probably related to https://bugzilla.gnome.org/show_bug.cgi?id=776391 Version-Release number of selected component: webkitgtk4-2.14.2-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 57 crash_function: WebCore::CoordinatedGraphicsLayer::notifyFlushRequired() executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess kernel: 4.8.14-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp
Created attachment 1234804 [details] File: backtrace
Created attachment 1234805 [details] File: core_backtrace
Created attachment 1234806 [details] File: dso_list
Created attachment 1234807 [details] File: limits
Created attachment 1234808 [details] File: namespaces
Created attachment 1234809 [details] File: proc_pid_status
Thanks for getting at this so fast! Shouldn't the bug status be "ASSIGNED", "POST" or "MODIFIED"?
I prefer to use Red Hat Bugzilla just as a to-do list for bugs to move upstream. Nobody is going to fix it here, so getting it upstream is the important thing. If we leave all the bugs opened once they've gone upstream we'd have an impossible to track mess. If you want to get updates on this issue, you can create a WebKit Bugzilla account and CC yourself on the upstream bug.