Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 590509 - [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:37283f0ca5bf09b5c719cdc28dc...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-10 01:08 UTC by Stephen Haffly
Modified: 2010-05-27 01:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-12 14:07:49 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (48.53 KB, text/plain)
2010-05-10 01:08 UTC, Stephen Haffly
no flags Details

Description Stephen Haffly 2010-05-10 01:08:55 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5/firefox
comment: I was checking out this web site. I had navigated through several pages, and clicked on a link for directions when Firefox closed.  I just went back and it did not close so I do not know if this was a one-time event or something that will happen again.
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.5/firefox
global_uuid: 37283f0ca5bf09b5c719cdc28dc335aab01d7e74
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. Open Firefox and navigate to http://www.thegroveaz.org/ministries/adult/what-is-grow-together/life-groups/
2. click on a link to navigate away from the page (page I wanted was http://www.thegroveaz.org/directions/)
3. Firefox closed and ABRT opened

Comment 1 Stephen Haffly 2010-05-10 01:08:59 UTC
Created attachment 412693 [details]
File: backtrace

Comment 2 Chris Campbell 2010-05-10 19:04:16 UTC
Thread 1 (Thread 18321):
#0  0x0000003b5ca0efbb in raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:42
        resultvar = 0
        pid = <value optimized out>
#1  0x0000003804a78d9a in nsProfileLock::FatalSignalHandler (signo=11)
    at nsProfileLock.cpp:212
        unblock_sigs = {__val = {1024, 0 <repeats 15 times>}}
        oldact = <value optimized out>
#2  <signal handler called>
No symbol table info available.
#3  NS_InvokeByIndex_P (that=0x7f486315ccdf, methodIndex=13, paramCount=1, 
    params=<value optimized out>) at xptcinvoke_x86_64_linux.cpp:208
        nr_stack = <value optimized out>
        gpregs = {0, 140735568425232, 0, 1, 139948719559488, 139948827039924}
        d0 = 0
        d5 = 0
        result = <value optimized out>
        nr_gpr = 2
        d1 = 0
        d6 = 0
        nr_fpr = 0
        d2 = 0
        d7 = 0
        methodAddress = Cannot access memory at address 0x3805a2525068

Fedora Bugzappers volunteer triage team

Comment 3 Chris Campbell 2010-05-10 19:05:31 UTC
Good repro steps. Very short trace.

This bug has been triaged

Fedora Bugzappers volunteer triage team

Comment 4 Martin Stransky 2010-05-10 21:06:18 UTC
Hm, unable to reproduce...can you reproduce the crash reliably?

Comment 5 Stephen Haffly 2010-05-11 20:01:48 UTC
My apologies for the delay.  My end-of-semester schedule has kept me busy so I am just now able to respond.

This is something that has not reoccurred since the one incident when Firefox crashed and the ABRT reported it.

Comment 6 Martin Stransky 2010-05-12 14:07:49 UTC
Okay, please reopen if you find any reproducer.

Comment 7 Need Real Name 2010-05-25 22:05:17 UTC
I just went through the ABRT reporting process, but my stacktrace and report apparently wasn't added to this bug since ABRT noticed it is 'CLOSED INSUFFICIENT_DATA' ... which is probably YAAB (Yet Another ABRT Bug).

In any case, I don't know if I have a reliable recreate; I was browsing our internal JIRA and clicked 'next' and ... boom.  Firefox abort.

Comment 8 Chris Campbell 2010-05-27 01:17:53 UTC
Actually, it was closed because the original reporter could not give us a reliable set of steps with which to reproduce the bug for troubleshooting. When your crash occurred, ABRT found your crash to be an exact duplicate of this one, so no need to upload the back-trace. If you can be more specific with your steps to enable us to reliably reproduce the crash, we can re-open this report for troubleshooting.

Fedora Bugzappers volunteer triage team

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