Bug 749762

Summary: [abrt] firefox-3.5.15-1.fc12: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dirk Hoffmann <hoffmann>
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: 12CC: gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:55b2c8c9119fec7138d515a16ff016d993d8308c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:21: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:
Attachments:
Description Flags
File: backtrace none

Description Dirk Hoffmann 2011-10-28 09:33:42 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.5/firefox
kernel: 2.6.32.26-175.fc12.i686.PAE
package: firefox-3.5.15-1.fc12
rating: 4
reason: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1319792925
uid: 500

How to reproduce
-----
1. Login to a MS SharePoint site
2. Using the "Sign out" option to logoff
3. FF crashed (reproducible)

The configuration is rather particular, using a portal for unified access, with filters for anonymous users. So if you cannot debug from the backtrace, it will be difficult to give you access to a similar system to reproduce the error.
Comment 1 Dirk Hoffmann 2011-10-28 09:33:46 UTC 
Created attachment 530633 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:21:36 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!