Bug 653663 - [abrt] firefox-3.6.12-1.fc13: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.12-1.fc13: Process /usr/lib/firefox-3.6/firefox was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 586565
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cd94f56cbae9130fe72336654af...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-15 21:32 UTC by Radek Vokál
Modified: 2018-04-11 10:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 22:39:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (58.70 KB, text/plain)
2010-11-15 21:32 UTC, Radek Vokál 		no flags Details
Part of the thread where crash happened (1.03 KB, text/plain)
2010-11-15 21:33 UTC, Matěj Cepl 		no flags Details
View All

Description Radek Vokál 2010-11-15 21:32:10 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox -UILocale cs https://bugzilla.redhat.com/show_bug.cgi?id=652817
comment: Happened several times
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.34.7-61.fc13.i686
package: firefox-3.6.12-1.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1289856395
uid: 500

How to reproduce
-----
1. Open several secure pages - in my case docspace instance behind krb access
2. Experience crash
3.
Comment 1 Radek Vokál 2010-11-15 21:32:13 UTC 
Created attachment 460673 [details]
File: backtrace
Comment 2 Matěj Cepl 2010-11-15 21:33:22 UTC 
Created attachment 460674 [details]
Part of the thread where crash happened
Comment 3 Matěj Cepl 2010-11-15 22:39:21 UTC 

*** This bug has been marked as a duplicate of bug 586565 ***
Note You need to log in before you can comment on or make changes to this bug.