Bug 1015462 - [abrt] midori-0.5.5-1.fc20: JSC::DFG::AssemblyHelpers::decodedCodeMapFor: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Summary: [abrt] midori-0.5.5-1.fc20: JSC::DFG::AssemblyHelpers::decodedCodeMapFor: Pro...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: midori
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8bfe0205aa580225c9787efb72c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 10:27 UTC by f.alexander.wilms
Modified: 2015-06-30 00:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:43:31 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (61.83 KB, text/plain)
2013-10-04 10:27 UTC, f.alexander.wilms
no flags Details
File: cgroup (159 bytes, text/plain)
2013-10-04 10:27 UTC, f.alexander.wilms
no flags Details
File: core_backtrace (32.91 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: dso_list (17.52 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: environ (1.38 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: limits (1.29 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: maps (71.62 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: open_fds (2.59 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: proc_pid_status (790 bytes, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details
File: var_log_messages (1.00 KB, text/plain)
2013-10-04 10:28 UTC, f.alexander.wilms
no flags Details

Description f.alexander.wilms 2013-10-04 10:27:51 UTC
Description of problem:
I was trying to report another bug in Midori and was adding a screenshot to the bug report.
URL launchpad.net/midori

Version-Release number of selected component:
midori-0.5.5-1.fc20

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        midori
crash_function: JSC::DFG::AssemblyHelpers::decodedCodeMapFor
executable:     /usr/bin/midori
kernel:         3.11.0-300.fc20.i686+PAE
runlevel:       N 5
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 JSC::DFG::AssemblyHelpers::decodedCodeMapFor at /lib/libjavascriptcoregtk-1.0.so.0
 #1 JSC::DFG::OSRExitCompiler::compileExit at /lib/libjavascriptcoregtk-1.0.so.0
 #2 compileOSRExit at /lib/libjavascriptcoregtk-1.0.so.0
 #3 ??
 #4 JSC::Interpreter::executeCall at /lib/libjavascriptcoregtk-1.0.so.0
 #5 JSC::call at /lib/libjavascriptcoregtk-1.0.so.0
 #6 WebCore::JSEventListener::handleEvent at /lib/libwebkitgtk-1.0.so.0
 #7 WebCore::EventTarget::fireEventListeners at /lib/libwebkitgtk-1.0.so.0
 #9 WebCore::Node::handleLocalEvents at /lib/libwebkitgtk-1.0.so.0
 #10 WebCore::EventContext::handleLocalEvents at /lib/libwebkitgtk-1.0.so.0

Potential duplicate: bug 920075

Comment 1 f.alexander.wilms 2013-10-04 10:27:55 UTC
Created attachment 807542 [details]
File: backtrace

Comment 2 f.alexander.wilms 2013-10-04 10:27:58 UTC
Created attachment 807543 [details]
File: cgroup

Comment 3 f.alexander.wilms 2013-10-04 10:28:01 UTC
Created attachment 807544 [details]
File: core_backtrace

Comment 4 f.alexander.wilms 2013-10-04 10:28:05 UTC
Created attachment 807545 [details]
File: dso_list

Comment 5 f.alexander.wilms 2013-10-04 10:28:08 UTC
Created attachment 807546 [details]
File: environ

Comment 6 f.alexander.wilms 2013-10-04 10:28:10 UTC
Created attachment 807547 [details]
File: limits

Comment 7 f.alexander.wilms 2013-10-04 10:28:14 UTC
Created attachment 807548 [details]
File: maps

Comment 8 f.alexander.wilms 2013-10-04 10:28:16 UTC
Created attachment 807549 [details]
File: open_fds

Comment 9 f.alexander.wilms 2013-10-04 10:28:19 UTC
Created attachment 807550 [details]
File: proc_pid_status

Comment 10 f.alexander.wilms 2013-10-04 10:28:23 UTC
Created attachment 807551 [details]
File: var_log_messages

Comment 11 Kevin Fenzi 2013-10-13 20:43:56 UTC
Can you duplicate the crash? Or was it a one time thing?

Comment 12 f.alexander.wilms 2013-10-14 09:00:44 UTC
I can't duplicate it. Maybe because I had uninstalled Midori in the meantime.

Comment 13 Fedora End Of Life 2015-05-29 09:30:49 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-30 00:43:31 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.


Note You need to log in before you can comment on or make changes to this bug.