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 613761 - [abrt] crash in firefox-3.6.4-1.fc13: MatchComponentType: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
[abrt] crash in firefox-3.6.4-1.fc13: MatchComponentType: Process /usr/lib64/...
Status: CLOSED NOTABUG
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:2c96e14a17d715576e2866e0644...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-12 14:58 EDT by Nathanael Noblet
Modified: 2010-07-13 07:02 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-12 22:02:17 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 (163.40 KB, text/plain)
2010-07-12 14:58 EDT, Nathanael Noblet
no flags Details

  None (edit)
Description Nathanael Noblet 2010-07-12 14:58:51 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
comment: I have no idea, I was away from my desk and came back to find firefox gone and abrt icon 
component: firefox
crash_function: MatchComponentType
executable: /usr/lib64/firefox-3.6/firefox
global_uuid: 2c96e14a17d715576e2866e064455841f3dc4139
kernel: 2.6.33.6-147.fc13.x86_64
package: firefox-3.6.4-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Leave FF running
2.
3.
Comment 1 Nathanael Noblet 2010-07-12 14:58:55 EDT
Created attachment 431243 [details]
File: backtrace
Comment 2 Nathanael Noblet 2010-07-12 22:02:17 EDT
likely a hardware issue on my end.

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