Bug 682103 - [abrt] firefox-3.6.13-2.el6_0 killed by signal 11 [@ nsBorderColors::~nsBorderColors]
Summary: [abrt] firefox-3.6.13-2.el6_0 killed by signal 11 [@ nsBorderColors::~nsBorde...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: firefox
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Stransky
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-04 06:36 UTC by Siddharth
Modified: 2018-11-14 14:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-20 15:09:25 UTC
Target Upstream Version:

Attachments (Terms of Use)
backtrace, disassembly (74.27 KB, text/plain)
2011-03-04 06:39 UTC, Siddharth 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.