thunderbird-bin crashed with SIGSEGV in raise()

Bug #144639 reported by Chad Bernier
8
Affects Status Importance Assigned to Milestone
thunderbird (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: thunderbird

This problem has been occuring for weeks now, but now that the crash report feature is working, I'm going to report it.

The problem occurs with my junk mail controls, which are pretty standard. The program opens, starts downloading the email from one of my accounts, then freezes. It should mark the mail as junk and move it to the junk folder. I close the frozen program, and reopen it. If there are no new emails, it's fine. I manually choose run junk mail controls, and it works fine. Then i repeat the process with my second account in there. This is pretty weird behavior, because running the junk mail controls works and downloading new mail works, but the act of letting it run junk mail controls automatically is causing the program to freeze.

ProblemType: Crash
Architecture: i386
Date: Wed Sep 19 20:32:55 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/thunderbird/thunderbird-bin
NonfreeKernelModules: ac97_bus
Package: thunderbird 2.0.0.6-0ubuntu4
PackageArchitecture: i386
ProcCmdline: /usr/lib/thunderbird/thunderbird-bin
ProcCwd: /home/chad
ProcEnviron:
 PATH=/home/chad/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: thunderbird
Stacktrace:
 #0 0xb7d89f5b in raise () from /lib/libpthread.so.0
 #1 0x08057966 in ?? ()
 #2 0x0000000b in ?? ()
 #3 0xbfad8cac in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 raise () from /lib/libpthread.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: thunderbird-bin crashed with SIGSEGV in raise()
Uname: Linux lappy486 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Chad Bernier (berniercr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:~nsCOMPtr_base (this=<value optimized out>) at nsCOMPtr.cpp:81
~nsInputStreamTransport (this=0x854eca8) at ../../../dist/include/xpcom/nsCOMPtr.h:542
nsInputStreamTransport::Release (this=0x854eca8) at nsStreamTransportService.cpp:107
nsCOMPtr_base::assign_with_AddRef (this=0x854dc50, rawPtr=0x0) at ./../glue/nsCOMPtr.h:531
nsMailboxProtocol::OnStopRequest (this=0x854dc38, request=0x8ea1c50, ctxt=0x8e6b7c8,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in thunderbird:
importance: Undecided → Medium
Revision history for this message
Alexander Sack (asac) wrote :

still reproducible?

Changed in thunderbird:
status: New → Incomplete
Revision history for this message
Joel Goguen (jgoguen) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
Joel Goguen (jgoguen) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Joel Goguen (jgoguen) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in thunderbird (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.