Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 622202 - [abrt] firefox-3.6.4-2.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
[abrt] firefox-3.6.4-2.fc14: Process /usr/lib64/firefox-3.6/firefox was kille...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
14
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:a900dd36bf607b169d3d94f0eab...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-07 23:38 EDT by Adam Williamson
Modified: 2011-12-07 08:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-07 08:10:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (77.86 KB, text/plain)
2010-08-07 23:38 EDT, Adam Williamson
no flags Details

  None (edit)
Description Adam Williamson 2010-08-07 23:38:23 EDT
abrt version: 1.1.10
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
comment: Wasn't doing anything, it was sitting idle.
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.35-0.57.rc6.git1.fc14.x86_64
package: firefox-3.6.4-2.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Branched)
time: 1281232940
uid: 501
Comment 1 Adam Williamson 2010-08-07 23:38:26 EDT
Created attachment 437402 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 08:10:04 EST
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@redhat.com).

Thanks!

Note You need to log in before you can comment on or make changes to this bug.