Bug 603974

Summary: [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jerry Amundson <jamundso>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:388187fac905da76dd750428223f072fd245aab1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-06 16:30:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Jerry Amundson 2010-06-15 03:38:36 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.6/firefox
global_uuid: 388187fac905da76dd750428223f072fd245aab1
kernel: 2.6.33.5-112.fc13.i686
package: firefox-3.6.3-4.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.entered a search, but not in the normal search bar - sorry I forget where.
2.
3.
Comment 1 Jerry Amundson 2010-06-15 03:38:37 UTC 
Created attachment 424025 [details]
File: backtrace
Comment 2 Jerry Amundson 2010-06-25 03:56:51 UTC 
Ping. Some love needed here. Consistently reproduced, on latest/greatest version, but always with unhelpful debuginfo. Could somebody step it up a notch please? Even just to give debugging instruction is fine.

Possibly related bugs:
bug #598761
bug #601898
bug #603974
Comment 3 Jerry Amundson 2010-07-06 16:30:36 UTC 
I can't reproduce, and it seems a dupe anyway.

*** This bug has been marked as a duplicate of bug 598761 ***