Bug 575052 - [abrt] crash in thunderbird-3.0.3-1.fc12 [@ SweepTearOffs]
Summary: [abrt] crash in thunderbird-3.0.3-1.fc12 [@ SweepTearOffs]
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Jan Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:82b0c95de13ad9c423a1afb2373...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-19 09:30 UTC by Matthew Booth
Modified: 2018-04-11 09:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-19 10:30:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (83.17 KB, text/plain)
2010-03-19 09:30 UTC, Matthew Booth
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 262509 0 None None None Never

Description Matthew Booth 2010-03-19 09:30:13 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
comment: I have 2 IMAP mailboxes configured and 2 remote calendars.
component: thunderbird
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
kernel: 2.6.32.9-70.fc12.x86_64
package: thunderbird-3.0.3-1.fc12
rating: 3
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
How to reproduce: Thunderbird has now crashed 3 times since applying this update yesterday morning. Each time Thunderbird has crashed I have not been actively using it at the time, so it is presumably triggered by some background task.

Comment 1 Matthew Booth 2010-03-19 09:30:20 UTC
Created attachment 401200 [details]
File: backtrace

Comment 2 Matěj Cepl 2010-03-19 10:16:43 UTC
#2  <signal handler called>
No symbol table info available.
#3  SweepTearOffs (table=<value optimized out>, hdr=<value optimized out>, 
    number=<value optimized out>, arg=<value optimized out>)
    at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mozilla/js/src/xpconnect/src/xpcinlines.h:697
        obj = 0x6d6f632e74616864
        marked = 0
        i = 1
        to = 0x7fd47167f660
        chunk = 0x7fd47167f660
#4  WrappedNativeTearoffSweeper (table=<value optimized out>, 
    hdr=<value optimized out>, number=<value optimized out>, 
    arg=<value optimized out>)
    at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mozilla/js/src/xpconnect/src/xpcwrappednativescope.cpp:568
No locals.
#5  0x000000335882c027 in JS_DHashTableEnumerate (table=0x7fd47fa16a00, etor=
    0x7fd48eb44403 <WrappedNativeTearoffSweeper(JSDHashTable*, JSDHashEntryHdr*, uint32, void*)>, arg=<value optimized out>)
    at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mozilla/js/src/jsdhash.cpp:724
        entryAddr = 0x7fd4797b6758 "aT\311\027"
        i = 246
        capacity = 8192
        entrySize = <value optimized out>
        ceiling = <value optimized out>
        didRemove = 0
        entryLimit = <value optimized out>
        entry = 0x7fd4797b6758
#6  0x00007fd48eb44623 in Enumerate ()
    at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mozilla/js/src/xpconnect/src/xpcmaps.h:165
No locals.
#7  XPCWrappedNativeScope::SweepAllWrappedNativeTearOffs ()
    at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mozilla/js/src/xpconnect/src/xpcwrappednativescope.cpp:577
        cur = 0x7fd484dfb980
#8  0x00007fd48eb2fdfa in XPCJSRuntime::GCCallback (cx=0x7fd48b64ec00, 
    status=<value optimized out>)
    at /usr/src/debug/thunderbird-3.0.3/comm-1.9.1/mozilla/js/src/xpconnect/src/xpcjsruntime.cpp:717
        threadLock = <value optimized out>
        data = {cx = 0x7fd48b64ec00, rt = 0x7fd49922c760}
        dyingWrappedJSArray = <value optimized out>
        self = 0x7fd49922c760
#9  0x00007fd489226a9e in DOMGCCallback (cx=<value optimized out>, status=

Comment 3 Matěj Cepl 2010-03-19 10:27:01 UTC
Reporter, could you please describe us what you have done to get to this point, and how we can reproduce this issue here? Is there anything special about your system, network, configuration which we need to replicate here in order to reproduce your problem please?

Comment 4 Matěj Cepl 2010-03-19 10:30:24 UTC
We found this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=262509) and believe that it is more appropriate to let it be resolved upstream.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.


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