Bug 1408225

Summary: [abrt] webkitgtk4: WebCore::CoordinatedGraphicsLayer::notifyFlushRequired()(): WebKitWebProcess killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Christian Stadelmann <fedora>
Component: webkitgtk4Assignee: Tomas Popela <tpopela>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: mcatanzaro+wrong-account-do-not-cc, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8f40c64232378c0be6228f44f157eec028b6aa38
Whiteboard: abrt_hash:dbd591c44e61228efe74131936b4af4d63c2dba6;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-22 15:31:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: dso_list
none
File: limits
none
File: namespaces
none
File: proc_pid_status none

Description Christian Stadelmann 2016-12-22 14:18:25 UTC
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

Comment 1 Christian Stadelmann 2016-12-22 14:18:30 UTC
Created attachment 1234804 [details]
File: backtrace

Comment 2 Christian Stadelmann 2016-12-22 14:18:31 UTC
Created attachment 1234805 [details]
File: core_backtrace

Comment 3 Christian Stadelmann 2016-12-22 14:18:33 UTC
Created attachment 1234806 [details]
File: dso_list

Comment 4 Christian Stadelmann 2016-12-22 14:18:34 UTC
Created attachment 1234807 [details]
File: limits

Comment 5 Christian Stadelmann 2016-12-22 14:18:35 UTC
Created attachment 1234808 [details]
File: namespaces

Comment 6 Christian Stadelmann 2016-12-22 14:18:37 UTC
Created attachment 1234809 [details]
File: proc_pid_status

Comment 7 Christian Stadelmann 2016-12-22 16:55:25 UTC
Thanks for getting at this so fast!

Shouldn't the bug status be "ASSIGNED", "POST" or "MODIFIED"?

Comment 8 Michael Catanzaro 2016-12-22 18:42:40 UTC
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.