Bug 643573 - [abrt] seamonkey-2.0.8-1.fc13: Process /usr/lib/seamonkey-2.0.8/seamonkey-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] seamonkey-2.0.8-1.fc13: Process /usr/lib/seamonkey-2.0.8/seamonkey-bin...
Keywords:
Status: CLOSED DUPLICATE of bug 612718
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bd58c8a8536876e7fa2f02d3afd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-16 02:56 UTC by dedanna
Modified: 2010-11-09 14:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:48:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.58 KB, text/plain)
2010-10-16 02:56 UTC, dedanna
no flags Details

Description dedanna 2010-10-16 02:56:07 UTC
abrt version: 1.1.13
architecture: i686
cmdline: /usr/lib/seamonkey-2.0.8/seamonkey-bin https://bugzilla.redhat.com/show_bug.cgi?id=641548
comment: When it crashed, it crashed 2.05 & 2.06-style.
component: seamonkey
crash_function: pthread_cond_timedwait@@GLIBC_2.3.2
executable: /usr/lib/seamonkey-2.0.8/seamonkey-bin
kernel: 2.6.34.7-56.fc13.i686
package: seamonkey-2.0.8-1.fc13
rating: 4
reason: Process /usr/lib/seamonkey-2.0.8/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1287197524
uid: 500

backtrace
-----
[New Thread 18684]
[New Thread 18685]
[New Thread 18686]
[New Thread 18687]
[New Thread 18692]
[New Thread 18693]
[New Thread 18695]
[New Thread 18696]
[New Thread 18759]
[New Thread 18802]
[New Thread 19729]
[New Thread 19754]
[New Thread 19755]
[New Thread 19757]
[New Thread 19758]
Core was generated by `/usr/lib/seamonkey-2.0.8/seamonkey-bin https://bugzilla.redhat.com/show_bug.cgi'.
Program terminated with signal 6, Aborted.
#0  0x00b30416 in __kernel_vsyscall ()

Thread 15 (Thread 19758):
#0  0x00b30416 in __kernel_vsyscall ()
No symbol table info available.
#1  0x009bc5d4 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_timedwait.S:236
No locals.
#2  0x0348a99e in pt_TimedWait (cv=0xb4e3eec4, ml=0xb4e22ee0, timeout=60000)
    at ../../../mozilla/nsprpub/pr/src/pthreads/ptsynch.c:292
        rv = <value optimized out>
        now = {tv_sec = 1287197509, tv_usec = 291448}
        tmo = {tv_sec = 1287197569, tv_nsec = 291448000}
        ticks = <value optimized out>
#3  0x0348b7d7 in PR_WaitCondVar (cvar=0xb4e3eec0, timeout=60000)
    at ../../../mozilla/nsprpub/pr/src/pthreads/ptsynch.c:419
        rv = <value optimized out>
        thred = 0x973f6110
#4  0x080e5d52 in nsHostResolver::GetHostToLookup (this=0xb4e1ad00, result=
    0x960ff17c) at nsHostResolver.cpp:773
        epoch = 3002287787
        timeout = 60000
        timedOut = <value optimized out>
        now = <value optimized out>
        lock = {<nsAutoLockBase> = {<No data fields>}, mLock = 0xb4e22ee0, 
          mLocked = 
Timeout exceeded: 60 second, killing gdb

How to reproduce
-----
1. I had closed out Seamonkey, except for the "install/update add-ons" window
2. Closed add-ons window
3. Seamonkey crashed

Comment 1 dedanna 2010-10-16 02:56:10 UTC
Created attachment 453830 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:48:23 UTC

*** This bug has been marked as a duplicate of bug 612718 ***

Comment 3 Karel Klíč 2010-11-09 14:48:23 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #612718.

Sorry for the inconvenience.


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