Bug 682103

Summary: [abrt] firefox-3.6.13-2.el6_0 killed by signal 11 [@ nsBorderColors::~nsBorderColors]
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: gecko-bugs-nobody, jwest, mishu, vgaikwad
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-20 15:09:25 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
backtrace, disassembly none

Description Siddharth 2011-03-04 06:36:22 UTC 
Description of problem:

abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
crash_function: raise
executable: /usr/lib64/firefox-3.6/firefox
rating: 0
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
time: 1297014160
uid: 501

Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux Client release 6.0 (Santiago)
firefox-3.6.13-2.el6_0

How reproducible:
Random crash

Actual results:
Firefox crashed.

Expected results:
Firefox should not crashed.

Additional info:
Comment 1 Siddharth 2011-03-04 06:39:21 UTC 
Created attachment 482232 [details]
backtrace, disassembly
Comment 3 RHEL Program Management 2011-04-04 02:35:44 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 4 Martin Stransky 2011-05-04 08:20:26 UTC 
Do you have any reproduction steps for this bug?
Comment 8 Martin Stransky 2011-10-20 15:09:25 UTC 
No reproducer, no fix.