Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 588887 - [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.5.9-2.fc12: Process /usr/lib64/firefox-3.5/firefox ...
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2552694d3d4dddddd1f7a9c380a...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-04 18:49 UTC by Pontus Enhager
Modified: 2010-12-03 15:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 15:05:42 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-04 18:49 UTC, Pontus Enhager
no flags Details

Description Pontus Enhager 2010-05-04 18:49:34 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox
comment: 100% reproducible on this machine with this certificate
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.5/firefox
global_uuid: 2552694d3d4dddddd1f7a9c380ac92ae6a160d38
package: firefox-3.5.9-2.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1.try to backup a certificate
2.after providing master password, firefox fails to backup certificate and crashes

Comment 1 Pontus Enhager 2010-05-04 18:49:38 UTC
Created attachment 411371 [details]
File: backtrace

Comment 2 Chris Campbell 2010-05-27 14:17:02 UTC
#2  <signal handler called>
No symbol table info available.
#3  0x0000003244094fe1 in nsCOMPtr_base::~nsCOMPtr_base (
    this=<value optimized out>, __in_chrg=<value optimized out>)
    at nsCOMPtr.cpp:81
No locals.
#4  0x0000003243f1af82 in ~nsCOMPtr (this=0x7fff170f92a0, 
    __in_chrg=<value optimized out>)
    at ../../../../dist/include/xpcom/nsCOMPtr.h:469
No locals.
#5  nsPKCS12Blob::~nsPKCS12Blob (this=0x7fff170f92a0, 
    __in_chrg=<value optimized out>) at nsPKCS12Blob.cpp:104
No locals.
#6  0x0000003243f2ec43 in nsNSSCertificateDB::ExportPKCS12File (
    this=<value optimized out>, aToken=<value optimized out>, aFile=
    0x7ff780739fc0, count=1, certs=0x7ff766fe9208)
    at nsNSSCertificateDB.cpp:1207
        locker = {<No data fields>}
        blob = {_vptr.nsPKCS12Blob = 0x32449280d0, mToken = 
    {<nsCOMPtr_base> = {mRawPtr = 0x7ff765fbf350}, <No data fields>}, 
          mCertArray = {<nsCOMPtr_base> = {mRawPtr = 0x0}, <No data fields>}, 
          mUIContext = {<nsCOMPtr_base> = {mRawPtr = 
    0x7ff75eda9080}, <No data fields>}, mTmpFile = 0x0, mTmpFilePath = 0x0, 
          mDigest = 0x0, mDigestIterator = 0x0, mTokenSet = 1}
        localRef = {<nsCOMPtr_base> = {mRawPtr = 
    0x7ff765fbf350}, <No data fields>}
#7  0x00000032440d1071 in NS_InvokeByIndex_P (that=0x7ff76fa12c00, 
    methodIndex=18, paramCount=4, params=<value optimized out>)
    at xptcinvoke_x86_64_linux.cpp:208
        nr_stack = <value optimized out>
        gpregs = {140733580286208, 0, 140700988710848, 1, 140700561609224, 
        d0 = <value optimized out>
        d5 = <value optimized out>
        result = <value optimized out>
        nr_gpr = 5
        d1 = <value optimized out>
        d6 = <value optimized out>
        nr_fpr = 0
        d2 = <value optimized out>
        d7 = <value optimized out>
        methodAddress = Cannot access memory at address 0x720065006c0041

Fedora Bugzappers volunteer triage team

Comment 3 Chris Campbell 2010-05-27 14:18:11 UTC
Steps listed, good back-trace, setting keyword.

This bug has been triaged

Fedora Bugzappers volunteer triage team

Comment 4 Bug Zapper 2010-11-03 15:39:22 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:

Comment 5 Bug Zapper 2010-12-03 15:05:42 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.