Bug 611553

Summary: [abrt] crash in firefox-3.5.10-1.fc12: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Steve Rogerson <steve.bz>
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: 12CC: gecko-bugs-nobody, greg, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:d718f01b9229ffb844536ca5098ef382d2fc67f9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-26 00:05:35 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
Part of the thread where crash happened none

Description Steve Rogerson 2010-07-05 15:11:18 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox
comment: Using firebug 
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.5/firefox
global_uuid: d718f01b9229ffb844536ca5098ef382d2fc67f9
kernel: 2.6.32.14-127.fc12.x86_64
package: firefox-3.5.10-1.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Steve Rogerson 2010-07-05 15:11:26 UTC 
Created attachment 429555 [details]
File: backtrace
Comment 2 greg 2010-07-13 02:22:32 UTC 
Package: firefox-3.5.10-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


Comment
-----
Right-click on a tab then "open this tab in a new window"
Comment 3 Matěj Cepl 2010-09-26 00:05:11 UTC 
Created attachment 449665 [details]
Part of the thread where crash happened
Comment 4 Matěj Cepl 2010-09-26 00:05:35 UTC 

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