Bug 606885 - [abrt] crash in thunderbird-3.0.4-2.fc12: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
[abrt] crash in thunderbird-3.0.4-2.fc12: Process /usr/lib64/thunderbird-3.0/...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: thunderbird (Show other bugs)
12
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:029a5f20dba0caee30ec734d23a...
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-22 12:36 EDT by Stephen John Smoogen
Modified: 2010-08-17 13:13 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-17 13:13:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (91.39 KB, text/plain)
2010-06-22 12:36 EDT, Stephen John Smoogen
no flags Details

  None (edit)
Description Stephen John Smoogen 2010-06-22 12:36:19 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
global_uuid: 029a5f20dba0caee30ec734d23a50b7c3beef297
kernel: 2.6.32.14-127.fc12.x86_64
package: thunderbird-3.0.4-2.fc12
rating: 4
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Started Thunderbird
2. Start typing passwords
3. Watch it crash
Comment 1 Stephen John Smoogen 2010-06-22 12:36:24 EDT
Created attachment 426007 [details]
File: backtrace
Comment 2 d. johnson 2010-08-17 13:13:33 EDT
#2  <signal handler called>
No symbol table info available.
#3  0x00000031cc0396e9 in nsCOMPtr_base::~nsCOMPtr_base (
    this=<value optimized out>, __in_chrg=<value optimized out>)
    at nsCOMPtr.cpp:81
No locals.
#4  0x00007fa7aae290de in ~nsCOMPtr (this=0x7fa79547eab0, 
    __in_chrg=<value optimized out>)
    at ../../../mozilla/dist/include/xpcom/nsCOMPtr.h:469
No locals.
#5  nsImapMailCopyState::~nsImapMailCopyState (this=0x7fa79547eab0, 
    __in_chrg=<value optimized out>)
    at /usr/src/debug/thunderbird-3.0.4/comm-1.9.1/mailnews/imap/src/nsImapMailFolder.cpp:7872
No locals.
#6  0x00007fa7aae2910f in nsImapMailCopyState::~nsImapMailCopyState (this=
    0x7fa79547eab0, __in_chrg=<value optimized out>)
    at /usr/src/debug/thunderbird-3.0.4/comm-1.9.1/mailnews/imap/src/nsImapMailFolder.cpp:7872
No locals.
#7  0x00007fa7aae28f3d in nsImapMailCopyState::Release (this=0x7fa79547eab0)
    at /usr/src/debug/thunderbird-3.0.4/comm-1.9.1/mailnews/imap/src/nsImapMailFolder.cpp:7875
        count = <value optimized out>
#8  0x00000031cc03ef30 in nsProxyReleaseEvent::Run (
    this=<value optimized out>) at nsProxyRelease.cpp:52
No locals.
#9  0x00000031cc06ab95 in nsThread::ProcessNextEvent (this=0x7fa7b304f160, 


Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them).

Unfortunately, we cannot use this backtrace.

Closing as INSUFFICIENT_DATA.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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