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 585531 - [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
[abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox ...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:9f1c33ba7459fec2c62f8972036...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-24 10:50 EDT by leon Cogs
Modified: 2010-04-30 23:47 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-04-30 23:47:21 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 (7.19 KB, text/plain)
2010-04-24 10:50 EDT, leon Cogs
no flags Details

  None (edit)
Description leon Cogs 2010-04-24 10:50:03 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
executable: /usr/lib64/firefox-3.6/firefox
global_uuid: 9f1c33ba7459fec2c62f8972036c159e1ae562e5
kernel: 2.6.33.2-57.fc13.x86_64
package: firefox-3.6.3-4.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 leon Cogs 2010-04-24 10:50:05 EDT
Created attachment 408838 [details]
File: backtrace
Comment 2 leon Cogs 2010-04-24 10:53:11 EDT
The crash has been happening lately when I exit firefox
Comment 3 Chris Campbell 2010-04-30 23:47:21 EDT
As it stands, the included back-trace appears to be incomplete and/or corrupted. If you are able to reproduce this crash, please resubmit a new back-trace.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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