Bug 95273

Summary: retrieving mail in the background
Product: [Unmaintained] kmail Reporter: Steve Whitlatch <swhitlat>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 1.7.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Steve Whitlatch 2004-12-16 17:22:30 UTC 
Version:           1.7.1 (using KDE 3.3.1, compiled sources)
Compiler:          gcc version 3.3.4
OS:                Linux (i686) release 2.6.9

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 10213)]
[KCrash handler]
#5  0x41d004b9 in QString::QString () from /usr/lib/qt/lib/libqt-mt.so.3
#6  0x40f80d47 in KIO::Scheduler::_assignJobToSlave ()
   from /opt/kde/lib/libkio.so.4
#7  0x4033aa6b in KMAcctExpPop::connectJob ()
   from /opt/kde/lib/libkmailprivate.so.0
#8  0x4033cbea in KMAcctExpPop::slotJobFinished ()
   from /opt/kde/lib/libkmailprivate.so.0
#9  0x4033f07e in KMAcctExpPop::slotResult ()
   from /opt/kde/lib/libkmailprivate.so.0
#10 0x4033f4c7 in KMAcctExpPop::qt_invoke ()
   from /opt/kde/lib/libkmailprivate.so.0
#11 0x41a2c18c in QObject::activate_signal ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#12 0x40f9c36a in KIO::Job::result () from /opt/kde/lib/libkio.so.4
#13 0x40f855cc in KIO::Job::emitResult () from /opt/kde/lib/libkio.so.4
#14 0x40f86acc in KIO::SimpleJob::slotFinished () from /opt/kde/lib/libkio.so.4
#15 0x40f89f1e in KIO::TransferJob::slotFinished ()
   from /opt/kde/lib/libkio.so.4
#16 0x40f9e34d in KIO::TransferJob::qt_invoke () from /opt/kde/lib/libkio.so.4
#17 0x41a2c18c in QObject::activate_signal ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#18 0x41a2bfb4 in QObject::activate_signal ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x40f797fe in KIO::SlaveInterface::finished ()
   from /opt/kde/lib/libkio.so.4
#20 0x40f783f9 in KIO::SlaveInterface::dispatch ()
   from /opt/kde/lib/libkio.so.4
#21 0x40f77919 in KIO::SlaveInterface::dispatch ()
   from /opt/kde/lib/libkio.so.4
#22 0x40f7516b in KIO::Slave::gotInput () from /opt/kde/lib/libkio.so.4
#23 0x40f76e88 in KIO::Slave::qt_invoke () from /opt/kde/lib/libkio.so.4
#24 0x41a2c18c in QObject::activate_signal ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#25 0x41a2c2ed in QObject::activate_signal ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#26 0x41d4e9f2 in QSocketNotifier::activated ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#27 0x41a48950 in QSocketNotifier::event () from /usr/lib/qt/lib/libqt-mt.so.3
#28 0x419cf84f in QApplication::internalNotify ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#29 0x419cee4e in QApplication::notify () from /usr/lib/qt/lib/libqt-mt.so.3
#30 0x4155e873 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4
#31 0x419bf25a in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#32 0x41979933 in QEventLoop::processEvents ()
   from /usr/lib/qt/lib/libqt-mt.so.3
#33 0x419e1ba8 in QEventLoop::enterLoop () from /usr/lib/qt/lib/libqt-mt.so.3
#34 0x419e1a58 in QEventLoop::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#35 0x419cfaa1 in QApplication::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#36 0x0804a3c4 in ?? ()
#37 0xbfffea70 in ?? ()
#38 0xbfffe980 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x41e532c0 in vtable for QGArray () from /usr/lib/qt/lib/libqt-mt.so.3
#42 0x42caee70 in ?? ()
#43 0x4004ca54 in getCustomHeap()::thBuf () from /usr/local/lib/libhoard.so
#44 0x00000001 in ?? ()
#45 0x404b60d0 in vtable for KMKernel () from /opt/kde/lib/libkmailprivate.so.0
#46 0x422e8549 in __libc_start_main () from /lib/libc.so.6
#47 0x422e8549 in __libc_start_main () from /lib/libc.so.6
#48 0x0804a121 in ?? ()
Comment 1 Steve Whitlatch 2004-12-16 17:29:41 UTC 
The Kmail crash occurred on an SMP system while using libhoard, a malloc substitute for SMP systems.
http://www.cs.umass.edu/~emery/hoard/

Just reporting the crash, not insisting that it is a bug with KDE/Kmail.
Comment 2 Thiago Macieira 2004-12-16 20:24:41 UTC 
Can you reproduce this crash at will?

Does the same problem happen if you aren't using that special library?
Comment 3 Thiago Macieira 2004-12-16 20:28:23 UTC 
Hmm... backtrace ends with the same two functions as Bug# 91614 and Bug #89615.

BTW, coolo, the dup-finder doesn't find a stacktrace in this report either.
Comment 4 Steve Whitlatch 2004-12-16 22:43:06 UTC 
> 20:24 ------- Can you reproduce this crash at will?
No. Kmail usually works good for me. The crash was an anomaly.

> Does the same problem happen if you aren't using that special library?

No, or rather, I don't know, or not yet. However, I know that this special 
library, libhoard, causes GNU emacs to segfault every time upon start (for me 
that is, won't start, segfaults), and, according to some of the documentation 
for libhoard, libhoard tends to expose application errors with respect to 
memory allocation.

In technical terms, it's a bit out of my understanding.

I have contacted the libhoard author. No response yet. 

This libhoard memory allocator is worth looking into. On SMP systems, it 
provides noticeable performance gains, even with just 2 processors. 

see ya, 

Steve Whitlatch
 






On Thursday 16 December 2004 12:24 pm, Thiago Macieira wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=95273
>
>
>
>
> ------- Additional Comments From thiago.macieira kdemail net  2004-12-16
> 20:24 ------- Can you reproduce this crash at will?
>
> Does the same problem happen if you aren't using that special library?
Comment 5 Till Adam 2005-01-02 12:19:56 UTC 

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