Bug 1048414

Summary: [abrt] midori: midori killed by SIGTRAP
Product: [Fedora] Fedora Reporter: imtkus
Component: midoriAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bjfleury, clayton.fyffe, cwellerding, darth.Serious, jason__m, jones.peter.busi, kevin, recon0000, tcfxfzoi
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/c7443e26946d3089eabab661048f306ee688889b
Whiteboard: abrt_hash:6917622a46cdc087a32ae32dbe0a5b4b8a78082d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:49:23 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description imtkus 2014-01-04 03:00:24 UTC 
Version-Release number of selected component:
midori-0.5.6-1.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/midori
executable:     /usr/bin/midori
kernel:         3.12.6-300.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 JSC::JITCode::execute at /lib/libjavascriptcoregtk-1.0.so.0
 #2 JSC::Interpreter::executeCall at /lib/libjavascriptcoregtk-1.0.so.0
 #3 JSC::call at /lib/libjavascriptcoregtk-1.0.so.0
 #4 WebCore::JSEventListener::handleEvent at /lib/libwebkitgtk-1.0.so.0
 #5 WebCore::EventTarget::fireEventListeners at /lib/libwebkitgtk-1.0.so.0
 #7 WebCore::Node::handleLocalEvents at /lib/libwebkitgtk-1.0.so.0
 #8 WebCore::EventContext::handleLocalEvents at /lib/libwebkitgtk-1.0.so.0
 #9 WebCore::EventDispatcher::dispatch at /lib/libwebkitgtk-1.0.so.0
 #10 WebCore::EventDispatchMediator::dispatchEvent at /lib/libwebkitgtk-1.0.so.0
Comment 1 imtkus 2014-01-04 03:00:30 UTC 
Created attachment 845192 [details]
File: backtrace
Comment 2 imtkus 2014-01-04 03:00:32 UTC 
Created attachment 845193 [details]
File: cgroup
Comment 3 imtkus 2014-01-04 03:00:35 UTC 
Created attachment 845194 [details]
File: core_backtrace
Comment 4 imtkus 2014-01-04 03:00:37 UTC 
Created attachment 845195 [details]
File: dso_list
Comment 5 imtkus 2014-01-04 03:00:40 UTC 
Created attachment 845196 [details]
File: environ
Comment 6 imtkus 2014-01-04 03:00:42 UTC 
Created attachment 845197 [details]
File: limits
Comment 7 imtkus 2014-01-04 03:00:46 UTC 
Created attachment 845198 [details]
File: maps
Comment 8 imtkus 2014-01-04 03:00:49 UTC 
Created attachment 845199 [details]
File: open_fds
Comment 9 imtkus 2014-01-04 03:00:52 UTC 
Created attachment 845200 [details]
File: proc_pid_status
Comment 10 imtkus 2014-01-04 03:00:54 UTC 
Created attachment 845201 [details]
File: var_log_messages
Comment 11 Kevin Fenzi 2014-01-04 16:55:39 UTC 
What were you doing when this happened?

Can you duplicate the crash?
Comment 12 Jason M 2014-03-09 18:28:16 UTC 
Another user experienced a similar problem:

New Fedora 20 install (System previously had Fedora Core 3-Fedora 18, but this install was clean).
Run YUM upgrade.
Run YUM install Seamonkey.
Run Seamonkey to initialize.  Close.
Run Midori to initiailze.  Close.
Run Midori Private Browsing.  Open new tab, go to https://www.google.com.  Run search for "Fedora".  Crash.

reporter:       libreport-2.1.12
backtrace_rating: 3
cmdline:        midori --private
executable:     /usr/bin/midori
kernel:         3.13.5-202.fc20.i686
package:        midori-0.5.7-1.fc20
reason:         midori killed by SIGILL
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 bjfleury 2014-04-15 21:20:38 UTC 
Another user experienced a similar problem:

Crashed while browsing website.

reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        midori
executable:     /usr/bin/midori
kernel:         3.11.10-301.fc20.i686+PAE
package:        midori-0.5.7-1.fc20
reason:         midori killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 kiyotaka saito 2014-05-10 17:26:24 UTC 
Another user experienced a similar problem:

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        midori
executable:     /usr/bin/midori
kernel:         3.14.3-200.fc20.i686+PAE
package:        midori-0.5.8-1.fc20
reason:         midori killed by SIGILL
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 Clayton Fyffe 2014-05-13 13:20:47 UTC 
Another user experienced a similar problem:

Log into Facebook, scroll down news feed.

Hangs for a few seconds, then exits with SIGILL.

If it helps, I am using older hardware:
AMD Athlon XP 1800+ (Doesn't have the newer instructions that most programs need now)
512 MB DDR
15 GB HDD (Btrfs)

It's more than likely because my CPU doesn't support SSE2.

reporter:       libreport-2.2.2
backtrace_rating: 3
cmdline:        midori
executable:     /usr/bin/midori
kernel:         3.14.3-200.fc20.i686+PAE
package:        midori-0.5.8-1.fc20
reason:         midori killed by SIGILL
runlevel:       N 5
type:           CCpp
uid:            1001
Comment 16 Chen_Min_Chin 2014-11-13 07:56:05 UTC 
Another user experienced a similar problem:

browse onedrive.live.com.

reporter:       libreport-2.2.3
backtrace_rating: 3
cmdline:        /usr/bin/midori
executable:     /usr/bin/midori
kernel:         3.17.2-200.fc20.i686+PAE
package:        midori-0.5.8-1.fc20
reason:         midori killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 17 Fedora End Of Life 2015-05-29 10:19:00 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 18 Fedora End Of Life 2015-06-30 00:49:23 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.