Bug 598970 - [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox ...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3b776194b1af8b1826437e2419d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 13:01 UTC by Rex Dieter
Modified: 2010-06-02 14:33 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-02 14:33:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (45.65 KB, text/plain)
2010-06-02 13:01 UTC, Rex Dieter 		no flags Details
View All

Description Rex Dieter 2010-06-02 13:01:53 UTC 
abrt 1.1.1 detected a crash.

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
global_uuid: 3b776194b1af8b1826437e2419d999a2b16f759b
kernel: 2.6.33.5-112.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)
How to reproduce: Upon launch, if I try to focus any input box or click any menu item, crashy crashy.
Comment 1 Rex Dieter 2010-06-02 13:01:54 UTC 
Created attachment 419021 [details]
File: backtrace
Comment 2 Rex Dieter 2010-06-02 13:04:35 UTC 
tried starting using:  'firefox -safe-mode' too, didn't help much.
Comment 3 Rex Dieter 2010-06-02 14:03:32 UTC 
Package: firefox-3.6.3-4.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
tried debugging for bug #598970 starting with 
firefox -safe-mode
but didn't seem to help.
Comment 4 Rex Dieter 2010-06-02 14:33:21 UTC 
hrm, my box had some other strange side-effects, and after a fresh boot, this seems no longer reproducible.  Let's consider it a bogon.
Note You need to log in before you can comment on or make changes to this bug.