Bug 693643

Summary: [abrt] firefox-3.6.16-1.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Nilesh Patil <npatil>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1c87f755a2c486e13f5a517f596e9e69736fff02
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:09:42 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
File: backtrace none

Description Nilesh Patil 2011-04-05 07:51:24 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 51867 bytes
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
Attached file: coredump, 360062976 bytes
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.x86_64
package: firefox-3.6.16-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301324370
uid: 500

How to reproduce
-----
Do not remember how it crashed. I apologize for provinding not enough info on it.

Comment 1 Nilesh Patil 2011-04-05 07:51:27 UTC
Created attachment 489932 [details]
File: backtrace

Comment 2 Nilesh Patil 2011-04-05 07:51:54 UTC
Package: firefox-3.6.16-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Do not remember how it crashed. I apologize for provinding not enough info on it.

Comment 3 Martin Stransky 2011-12-07 13:09:42 UTC
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

Thanks!