Bug 589328 - [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib/firefox-3.5/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib/firefox-3.5/firefox wa...
Status: CLOSED DUPLICATE of bug 538207
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:047c7e3f362cfed2537a7a8b201...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-05 21:01 UTC by Stuart D Gathman
Modified: 2010-05-27 13:37 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-05-27 13:37:26 UTC

Attachments (Terms of Use)
File: backtrace (30.32 KB, text/plain)
2010-05-05 21:01 UTC, Stuart D Gathman 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Stuart D Gathman 2010-05-05 21:01:39 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5/firefox
comment: There are a number of log entries, so this isn't an isolated instance.
component: firefox
executable: /usr/lib/firefox-3.5/firefox
global_uuid: 047c7e3f362cfed2537a7a8b201430ecdd6d213f
kernel: 2.6.32.9-70.fc12.i686
package: firefox-3.5.9-2.fc12
rating: 4
reason: Process /usr/lib/firefox-3.5/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Close firefox window
2.
3.
Comment 1 Stuart D Gathman 2010-05-05 21:01:41 UTC 
Created attachment 411736 [details]
File: backtrace
Comment 2 Chris Campbell 2010-05-27 13:37:26 UTC 
Thank you for taking the time to make this bug report.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



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

*** This bug has been marked as a duplicate of bug 538207 ***
Note You need to log in before you can comment on or make changes to this bug.