Bug 920075

Summary: [abrt] midori-0.4.7-2.fc18: JSC::DFG::AssemblyHelpers::decodedCodeMapFor: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93
Component: midoriAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, kevin
Target Milestone: ---Flags: kevin: needinfo?
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:8bfe0205aa580225c9787efb72c547040791b50a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 23:05: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: build_ids
none
File: core_backtrace
none
File: dso_list
none
File: limits
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages none

Description 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:30 UTC
Version-Release number of selected component:
midori-0.4.7-2.fc18

Additional info:
backtrace_rating: 3
cmdline:        midori -p risky.biz
crash_function: JSC::DFG::AssemblyHelpers::decodedCodeMapFor
executable:     /usr/bin/midori
kernel:         3.8.1-201.fc18.i686
uid:            1000

Truncated backtrace:
Thread no. 1 (7 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::execute at /lib/libjavascriptcoregtk-1.0.so.0
 #5 arrayProtoFuncForEach at /lib/libjavascriptcoregtk-1.0.so.0
 #6 ??

Comment 1 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:36 UTC
Created attachment 708284 [details]
File: backtrace

Comment 2 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:38 UTC
Created attachment 708285 [details]
File: build_ids

Comment 3 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:41 UTC
Created attachment 708286 [details]
File: core_backtrace

Comment 4 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:43 UTC
Created attachment 708287 [details]
File: dso_list

Comment 5 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:45 UTC
Created attachment 708288 [details]
File: limits

Comment 6 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:47 UTC
Created attachment 708289 [details]
File: proc_pid_status

Comment 7 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:50 UTC
Created attachment 708290 [details]
File: smolt_data

Comment 8 6663bcdbe265d507c8d8cd7d8898d05c8d0c2a93 2013-03-11 10:08:52 UTC
Created attachment 708291 [details]
File: var_log_messages

Comment 9 Kevin Fenzi 2013-03-11 14:49:04 UTC
Can you duplicate this crash? Or was it a onetime thing?

Comment 10 Fedora End Of Life 2013-12-21 15:25:40 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 11 Fedora End Of Life 2014-02-05 23:05:23 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.