Bug 1133230

Summary: [abrt] epiphany: WebKit::WebTextCheckerClient::guessesForWord(): epiphany killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Wouter <heyveld>
Component: webkitgtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ByteEnable, debarshir, fedora, gecko-bugs-nobody, kalevlember, mcatanzaro, mclasen, rob.townley, tcfxfzoi, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/32bf3a076ddc2ea1f1b27f711e8029ebca9c006d
Whiteboard: abrt_hash:6ae73ae5243494330557862393960ee1327083d3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:13:13 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Wouter 2014-08-23 15:34:47 UTC 
Description of problem:
While working in an external mysql/phpMyAdmin environment in the Epiphany - webbrowser I copied the content of a table, Epiphany crashed.

Version-Release number of selected component:
epiphany-3.10.3-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        epiphany
crash_function: WebKit::WebTextCheckerClient::guessesForWord
executable:     /usr/bin/epiphany
kernel:         3.15.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 WebKit::WebTextCheckerClient::guessesForWord at Source/WebKit2/Shared/ImmutableArray.h:65
 #1 callMemberFunction<WebKit::WebPageProxy, void (WebKit::WebPageProxy::*)(WTF::String const&, WTF::String const&, WTF::Vector<WTF::String>&), WTF::String, WTF::String, WTF::Vector<WTF::String> > at Source/WebKit2/Platform/CoreIPC/HandleMessage.h:131
 #2 CoreIPC::handleMessage<Messages::WebPageProxy::GetGuessesForWord, WebKit::WebPageProxy, void (WebKit::WebPageProxy::*)(WTF::String const&, WTF::String const&, WTF::Vector<WTF::String, 0ul, WTF::CrashOnOverflow>&)> at Source/WebKit2/Platform/CoreIPC/HandleMessage.h:387
 #3 WebKit::WebPageProxy::didReceiveSyncMessage at DerivedSources/WebKit2/WebPageProxyMessageReceiver.cpp:879
 #4 CoreIPC::MessageReceiverMap::dispatchSyncMessage at Source/WebKit2/Platform/CoreIPC/MessageReceiverMap.cpp:103
 #5 WebKit::ChildProcessProxy::dispatchSyncMessage at Source/WebKit2/Shared/ChildProcessProxy.cpp:112
 #6 WebKit::WebProcessProxy::didReceiveSyncMessage at Source/WebKit2/UIProcess/WebProcessProxy.cpp:380
 #7 CoreIPC::Connection::dispatchSyncMessage at Source/WebKit2/Platform/CoreIPC/Connection.cpp:754
 #8 CoreIPC::Connection::dispatchMessage at Source/WebKit2/Platform/CoreIPC/Connection.cpp:814
 #9 CoreIPC::Connection::dispatchOneMessage at Source/WebKit2/Platform/CoreIPC/Connection.cpp:842
Comment 1 Wouter 2014-08-23 15:34:50 UTC 
Created attachment 929919 [details]
File: backtrace
Comment 2 Wouter 2014-08-23 15:34:51 UTC 
Created attachment 929920 [details]
File: cgroup
Comment 3 Wouter 2014-08-23 15:34:53 UTC 
Created attachment 929921 [details]
File: core_backtrace
Comment 4 Wouter 2014-08-23 15:34:54 UTC 
Created attachment 929922 [details]
File: dso_list
Comment 5 Wouter 2014-08-23 15:34:55 UTC 
Created attachment 929923 [details]
File: environ
Comment 6 Wouter 2014-08-23 15:34:56 UTC 
Created attachment 929924 [details]
File: exploitable
Comment 7 Wouter 2014-08-23 15:34:57 UTC 
Created attachment 929925 [details]
File: limits
Comment 8 Wouter 2014-08-23 15:34:59 UTC 
Created attachment 929926 [details]
File: maps
Comment 9 Wouter 2014-08-23 15:35:00 UTC 
Created attachment 929927 [details]
File: open_fds
Comment 10 Wouter 2014-08-23 15:35:01 UTC 
Created attachment 929928 [details]
File: proc_pid_status
Comment 11 Wouter 2014-08-23 15:35:02 UTC 
Created attachment 929929 [details]
File: var_log_messages
Comment 12 Michael Catanzaro 2015-04-04 21:21:16 UTC 
*** Bug 1154905 has been marked as a duplicate of this bug. ***
Comment 13 Fedora End Of Life 2015-05-29 12:42:56 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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.
Comment 14 Fedora End Of Life 2015-06-29 22:13:13 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.