Bug 698472 - [abrt] firefox-3.6.16-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.16-1.fc13: Process /usr/lib64/firefox-3.6/firefox was kill...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bab13445db3a210a1eb62fc0cd0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-20 23:24 UTC by Jerry Uanino
Modified: 2011-04-21 01:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-21 01:41:44 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (98.42 KB, text/plain)
2011-04-20 23:24 UTC, Jerry Uanino 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jerry Uanino 2011-04-20 23:24:33 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.34.8-68.fc13.x86_64
package: firefox-3.6.16-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1303301461
uid: 500

How to reproduce
-----
1. upgrade from fedora 12 to fedora 13
2. open xwindows
3. open firefox
Comment 1 Jerry Uanino 2011-04-20 23:24:35 UTC 
Created attachment 493661 [details]
File: backtrace
Comment 2 Jerry Uanino 2011-04-20 23:26:05 UTC 
-safe-mode works, must be bug in a plugin.
Comment 3 Jerry Uanino 2011-04-21 01:41:44 UTC 
no idea what it was, cleaned up old plugins and works fine. i'll close this, no reason for someone to waste time debugging, but figured someone might get the same problem so this matching bug would lead them to turning off their plugins by running in safe mode to correct.
Note You need to log in before you can comment on or make changes to this bug.