Bug 626048 - [abrt] crash in firefox-3.5.11-1.fc12: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
[abrt] crash in firefox-3.5.11-1.fc12: Process /usr/lib/firefox-3.5/firefox w...
Status: CLOSED DUPLICATE of bug 616556
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:11a46708ac09f81bc91f025989d...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-21 12:20 EDT by Stefanvde
Modified: 2018-04-11 03:31 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-25 20:06:36 EDT
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 (102.30 KB, text/plain)
2010-08-21 12:20 EDT, Stefanvde
no flags Details
Part of the thread where crash happened (907 bytes, text/plain)
2010-09-25 20:06 EDT, Matěj Cepl
no flags Details

  None (edit)
Description Stefanvde 2010-08-21 12:20:15 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.5/firefox
global_uuid: 11a46708ac09f81bc91f025989dd57c520087f02
kernel: 2.6.32.16-150.fc12.i686.PAE
package: firefox-3.5.11-1.fc12
rating: 4
reason: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Stefanvde 2010-08-21 12:20:24 EDT
Created an attachment (id=440140)
File: backtrace
Comment 2 Matěj Cepl 2010-09-25 20:06:17 EDT
Created attachment 449667 [details]
Part of the thread where crash happened
Comment 3 Matěj Cepl 2010-09-25 20:06:36 EDT

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

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