Bug 691993 - [abrt] firefox-3.6.16-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.16-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:633283b5684c905c05d89e573c9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-30 06:22 UTC by Alexander Kurtakov
Modified: 2011-06-28 10:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-28 10:36:35 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (34.38 KB, text/plain)
2011-03-30 06:22 UTC, Alexander Kurtakov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alexander Kurtakov 2011-03-30 06:22:24 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 35205 bytes
cmdline: /usr/lib/firefox-3.6/firefox https://bugzilla.redhat.com/show_bug.cgi?id=691699
comment: If there is nothing usable in the backtrace please close immediately. This bug is purely to enable you looking at the backtrace.
component: firefox
Attached file: coredump, 282923008 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.i686
package: firefox-3.6.16-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301464687
uid: 500

How to reproduce
-----
1. firefox crashed while being minimized
2.
3.
Comment 1 Alexander Kurtakov 2011-03-30 06:22:27 UTC 
Created attachment 488653 [details]
File: backtrace
Comment 2 Alexander Kurtakov 2011-06-28 10:36:35 UTC 
I have no way to test 3.6 anymore. Closing the bug as I'm no longer interested.
Note You need to log in before you can comment on or make changes to this bug.