Bug 788363

Summary: Process /usr/lib/chromium-browser/chromium-browser was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Flos Lonicerae <lonicerae>
Component: chromium-bsuAssignee: Hans de Goede <hdegoede>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 14:29:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
smolt data
none
back trace
none
bug report text
none
build ids
none
cmdline
none
comment
none
crash function
none
dso list
none
duphash
none
environ
none
maps
none
kernel
none
package none

Description Flos Lonicerae 2012-02-08 06:25:29 UTC
open webqq.qq.com. this can always repeat the bug.

i can NOT find an bug report item for chromium, so report the bug here, sorry.

Comment 1 Flos Lonicerae 2012-02-08 06:26:40 UTC
Created attachment 560146 [details]
smolt data

Comment 2 Flos Lonicerae 2012-02-08 06:27:15 UTC
Created attachment 560147 [details]
back trace

Comment 3 Flos Lonicerae 2012-02-08 06:27:49 UTC
Created attachment 560148 [details]
bug report text

Comment 4 Flos Lonicerae 2012-02-08 06:28:14 UTC
Created attachment 560149 [details]
build ids

Comment 5 Flos Lonicerae 2012-02-08 06:28:35 UTC
Created attachment 560150 [details]
cmdline

Comment 6 Flos Lonicerae 2012-02-08 06:28:59 UTC
Created attachment 560151 [details]
comment

Comment 7 Flos Lonicerae 2012-02-08 06:29:24 UTC
Created attachment 560152 [details]
crash function

Comment 8 Flos Lonicerae 2012-02-08 06:29:50 UTC
Created attachment 560153 [details]
dso list

Comment 9 Flos Lonicerae 2012-02-08 06:30:18 UTC
Created attachment 560154 [details]
duphash

Comment 10 Flos Lonicerae 2012-02-08 06:30:46 UTC
Created attachment 560155 [details]
environ

Comment 11 Flos Lonicerae 2012-02-08 06:31:16 UTC
Created attachment 560156 [details]
maps

Comment 12 Flos Lonicerae 2012-02-08 06:31:41 UTC
Created attachment 560157 [details]
kernel

Comment 13 Flos Lonicerae 2012-02-08 06:32:15 UTC
Created attachment 560158 [details]
package

Comment 14 Flos Lonicerae 2012-02-08 06:32:45 UTC
this problem seems also affect firefox.

Comment 15 Fedora End Of Life 2013-01-16 13:38:18 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Fedora End Of Life 2013-02-13 14:30:00 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.