Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 598970 - [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
[abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib64/firefox-3.6/firefox ...
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-06-02 09:01 EDT by Rex Dieter
Modified: 2010-06-02 10:33 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-02 10:33:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Rex Dieter 2010-06-02 09:01:53 EDT
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
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 09:01:54 EDT
Created attachment 419021 [details]
File: backtrace
Comment 2 Rex Dieter 2010-06-02 09:04:35 EDT
tried starting using:  'firefox -safe-mode' too, didn't help much.
Comment 3 Rex Dieter 2010-06-02 10:03:32 EDT
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 10:33:21 EDT
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.