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 620252 - [abrt] crash in firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
[abrt] crash in firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox ...
Status: CLOSED DUPLICATE of bug 625350
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-01 15:06 EDT by Peter Fuchs
Modified: 2018-04-11 05:20 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-26 12:50:25 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (82.90 KB, text/plain)
2010-08-01 15:06 EDT, Peter Fuchs
no flags Details
Part of the thread where crash happened (1.04 KB, text/plain)
2010-11-26 11:44 EST, Matěj Cepl
no flags Details

  None (edit)
Description Peter Fuchs 2010-08-01 15:06:30 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
global_uuid: add0d95836939ae887ed700acd4453b528ce9e96
package: firefox-3.6.7-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Peter Fuchs 2010-08-01 15:06:34 EDT
Created attachment 435909 [details]
File: backtrace
Comment 2 jupi32000 2010-08-18 00:54:08 EDT
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)

Browsed pc.ign.com
Comment 3 Matěj Cepl 2010-11-26 11:44:46 EST
Created attachment 463100 [details]
Part of the thread where crash happened
Comment 4 Matěj Cepl 2010-11-26 12:50:25 EST

*** This bug has been marked as a duplicate of bug 625350 ***

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