Bug 697973

Summary: [abrt] firefox-3.6.16-1.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: edo <edosurina>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:28c599092ac1fb0883058e3354b6332e4680f3cd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:23:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description edo 2011-04-19 19:41:28 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 63476 bytes
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale sk https://www.google.com/accounts/ServiceLoginAuth?ltmpl=yj_wsad&ltmplcache=2&continue=https%3A%2F%2Fmail%2Egoogle%2Ecom%2Fmail&service=mail&rm=false&ltmpl=yj_wsad&Email=edosurina%40gmail%2Ecom&Passwd=ninkaedko&rmShown=1&null=Sign+in
component: firefox
Attached file: coredump, 108650496 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.35.12-88.fc14.x86_64
package: firefox-3.6.16-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303241803
uid: 500

How to reproduce
-----
1.start PC and Gnome session
2.start CheckGmail v1.13svn
3.crash
Comment 1 edo 2011-04-19 19:41:32 UTC 
Created attachment 493271 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:23:55 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

Thanks!