*** Bug 122085 has been marked as a duplicate of this bug. ***

Just want to report that I have the same problem when transferring large amounts of mail (e.g. when using a filter on an IMAP inbox to transfer to a local folder). 

*** Bug 130732 has been marked as a duplicate of this bug. ***

Comfirming with KMail 1.9.3 (Debian Sid package).

Reliable steps to provoke this crash:
1. Start writing a new mail.
2. Press Ctrl+P twice (this opens two print dialogs).
3. Close both print dialogs.
4. KMail crashes.

I don't use IMAP at all.

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1478687040 (LWP 12833)]
[New Thread -1508754512 (LWP 12837)]
[New Thread -1500361808 (LWP 12836)]
[New Thread -1491969104 (LWP 12835)]
[New Thread -1483576400 (LWP 12834)]
[KCrash handler]
#6  0x4e693ff8 in KMMessage::setTransferInProgress (this=0x93c05f0, 
    value=false, force=false)
    at /tmp/buildd/kdepim-3.5.3/build-tree/kdepim-3.5.3/kmail/kmmessage.cpp:244
#7  0x4e88eff0 in KMCommand::slotPostTransfer (this=0x92f1d50, 
    result=KMCommand::OK)
    at /tmp/buildd/kdepim-3.5.3/build-tree/kdepim-3.5.3/kmail/kmcommands.cpp:264
#8  0x4e896c06 in KMCommand::qt_invoke (this=0x92f1d50, _id=5, _o=0xafb64434)
    at ./kmcommands.moc:148
#9  0x4e8971db in KMPrintCommand::qt_invoke (this=0x92f1d50, _id=5, 
    _o=0xafb64434) at ./kmcommands.moc:1901
#10 0x4cadb54b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x4e88f35e in KMCommand::messagesTransfered (this=0x92f1d50, 
    t0=KMCommand::OK) at ./kmcommands.moc:126
#12 0x4e897c39 in KMCommand::slotStart (this=0x92f1d50)
    at /tmp/buildd/kdepim-3.5.3/build-tree/kdepim-3.5.3/kmail/kmcommands.cpp:235
#13 0x4e896c18 in KMCommand::qt_invoke (this=0x92f1d50, _id=4, _o=0xafb64548)
    at ./kmcommands.moc:147
#14 0x4e8971db in KMPrintCommand::qt_invoke (this=0x92f1d50, _id=4, 
    _o=0xafb64548) at ./kmcommands.moc:1901
#15 0x4cadb54b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0x4ce6d1a9 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#17 0x4caf8c4c in QSignal::activate () from /usr/lib/libqt-mt.so.3
#18 0x4cb00710 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#19 0x4ca7187a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0x4ca71a76 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0x4d15332e in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0x4ca03001 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#23 0x4ca63305 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#24 0x4ca16d2a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0x4ca8a255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0x4ca8a17a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0x4ca7038d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x0804a094 in main (argc=153836208, argv=0x84d7df8)
    at /tmp/buildd/kdepim-3.5.3/build-tree/kdepim-3.5.3/kmail/main.cpp:110
#29 0x4a2cdeb0 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x08049e11 in _start () at ../sysdeps/i386/elf/start.S:119

*** Bug 134927 has been marked as a duplicate of this bug. ***

*** Bug 138668 has been marked as a duplicate of this bug. ***

I can't reproduce two print dialogs. But others (Steffen) seem to be able to reproduce this at will - any chance I can get a valgrind log? Just valgrind kmail --nofork

This is when running under valgrind:
<no crash, logs at

--nocrashhandler --nofork
http://www.inb.uni-luebeck.de/~moeller/kmail_valgrind.log.29978

--nofork
http://www.inb.uni-luebeck.de/~moeller/kmail_valgrind.log.30233

I tried to HAMmify several sets of emails

>
this is when running without valgrind, the first selection of three emails als ham surprisingly worked, the next selection of 8 or so failed (was meaner in my valgrind tests, and I started that kmail beast twice):

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1249773872 (LWP 30343)]
[New Thread -1277310064 (LWP 30347)]
[New Thread -1268921456 (LWP 30346)]
[New Thread -1260532848 (LWP 30345)]
[New Thread -1252144240 (LWP 30344)]
[KCrash handler]
#5  0xb7bc7588 in KMMessage::setTransferInProgress (this=0x84a51f8, 
    value=false, force=false)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./kmail/kmmessage.cpp:248
#6  0xb7bd5a10 in KMCommand::slotPostTransfer (this=0x86167f8, 
    result=KMCommand::OK)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./kmail/kmcommands.cpp:265
#7  0xb7c6d676 in KMCommand::qt_invoke (this=0x86167f8, _id=5, _o=0xbfe5db94)
    at ./kmcommands.moc:148
#8  0xb7c6dc7b in KMFilterActionCommand::qt_invoke (this=0x86167f8, _id=5, 
    _o=0xbfe5db94) at ./kmcommands.moc:2485
#9  0xb7089d4f in QObject::activate_signal (this=0x86167f8, clist=0x83907d0, 
    o=0xbfe5db94) at kernel/qobject.cpp:2356
#10 0xb7bd5b9e in KMCommand::messagesTransfered (this=0x86167f8, 
    t0=KMCommand::OK) at ./kmcommands.moc:126
#11 0xb7c6d58d in KMCommand::slotJobFinished (this=0x86167f8)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./kmail/kmcommands.cpp:404
#12 0xb7c6d642 in KMCommand::qt_invoke (this=0x86167f8, _id=7, _o=0xbfe5dcdc)
    at ./kmcommands.moc:150
#13 0xb7c6dc7b in KMFilterActionCommand::qt_invoke (this=0x86167f8, _id=7, 
    _o=0xbfe5dcdc) at ./kmcommands.moc:2485
#14 0xb7089d4f in QObject::activate_signal (this=0x84e5b00, clist=0x84ddeb8, 
    o=0xbfe5dcdc) at kernel/qobject.cpp:2356
#15 0xb708a7e0 in QObject::activate_signal (this=0x84e5b00, signal=7)
    at kernel/qobject.cpp:2325
#16 0xb7bb7a5c in KMail::FolderJob::finished (this=0x84e5b00)
    at ./folderjob.moc:188
#17 0xb7c65658 in ~FolderJob (this=0x84e5b00)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./kmail/folderjob.cpp:98
#18 0xb7d5c415 in ~ImapJob (this=0x84e5b00)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./kmail/imapjob.cpp:271
#19 0xb708941e in QObject::event (this=0x84e5b00, e=0x84ddf18)
    at kernel/qobject.cpp:750
#20 0xb7021c26 in QApplication::internalNotify (this=0xbfe5e330, 
    receiver=0x84e5b00, e=0x84ddf18) at kernel/qapplication.cpp:2635
#21 0xb7023a43 in QApplication::notify (this=0xbfe5e330, receiver=0x84e5b00, 
    e=0x84ddf18) at kernel/qapplication.cpp:2358
#22 0xb7729c3e in KApplication::notify (this=0xbfe5e330, receiver=0x84e5b00, 
    event=0x84ddf18)
    at /tmp/buildd/kdelibs-3.5.6.r1.dfsg.1/./kdecore/kapplication.cpp:550
#23 0xb6fb5421 in QApplication::sendEvent (receiver=0x84e5b00, 
    event=0x84ddf18) at ../include/qapplication.h:520
#24 0xb7022c4e in QApplication::sendPostedEvents (receiver=0x0, event_type=0)
    at kernel/qapplication.cpp:3299
#25 0xb7022d56 in QApplication::sendPostedEvents ()
    at kernel/qapplication.cpp:3210
#26 0xb6fc8c55 in QEventLoop::processEvents (this=0x80884d0, flags=4)
    at kernel/qeventloop_x11.cpp:144
#27 0xb703c179 in QEventLoop::enterLoop (this=0x80884d0)
    at kernel/qeventloop.cpp:198
#28 0xb703bf9a in QEventLoop::exec (this=0x80884d0)
    at kernel/qeventloop.cpp:145
#29 0xb70237bf in QApplication::exec (this=0xbfe5e330)
    at kernel/qapplication.cpp:2758
#30 0x0804a094 in main (argc=0, argv=0x0)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./kmail/main.cpp:110
#31 0xb77e1ea8 in __libc_start_main () from /lib/libc.so.6
#32 0x08049e11 in _start () at ../sysdeps/i386/elf/start.S:119

Good luck!

My very personal hunch is that valgrind's default settings prevent the missinterpretation of some undefined variable of which there are many reported. Well, ... enjoy.

Many thanks for looking into this

Steffen

The system is the latest from unstable and experimental.

I'm hoping this will be fixed by the 113885 fix.  Can anyone able to reproduce this try 3.5 svn?

I can confirm a general problem, also when using IMAP.  When doing _any_ operation that involves a large amount of mail (perhaps 500+), kmail regularly hangs or crashes or otherwise fails.  There may be several separate underlying issues, but the general result is the same.  

In my case, we have monitoring apps that are known to go haywire occasionally and flood me with 1-2k mails.  This usually means I have to fire up almost any other mail client to handle it, because kmail will inevitably crash.

Could this have something to do with the progress window?  Creating a separate progress bar for every mail being moved/deleted seems like a really bad thing when one has to delete 2000 mails... (Although these problems don't appear with local mailboxes, only IMAP)

Some results when doing the following actions on roughly 300 - 500+ mails in an IMAP box (servers have been cyrus, dovecot and exchange)

Delete (move to trash) - Hangs fairly quickly, usually have to kill 
Shift+Delete - Seems fine at first, then UI hangs (over 30 minutes on 1500 mails, eventually had to kill -9)
Apply filters (Ctrl+J) - Any attempt to do this on more than about 150 mails results in hangs, crashes and/or lost mails. This applies to every version of kmail I've used for a couple years.  I've disavowed IMAP filtering completely.
Move IMAP -> Local - Usually works ok.  Minor hangs w/ 1500+ mails.
Move Local -> IMAP - 50% chance of crash or hang
Viewing/Refreshing any large folder of 1k+ mails - about a 10% chance that the list view will go blank.  Can usually fix this by unfocusing/refocusing the large folder.

If there is any hard data you would like, let me know (doing a debug build as I write this).

Currently on
KDE 3.5.6
Kmail 1.9.1

-Mike Culbertson

Steffen: I'm not allwed to access the files ;(
BTW: how's Luebeck these days? ;)

Stephan,

I am sorry, it should work now....who constrained my umask so much ...

Luebeck is sunny. get the weather report applet and choose 
Luebeck-Blankensee. :o)  The Unesco heritage is still here and (good to 
mention both in one sentence) we have the user meeting of the NorduGrid 
(www.nordugrid.org) in Luebeck on May 2nd-4th.... just in case that any kmail 
users that are monitoring this bug are also interested in Grid computing.

Many greetings

Steffen

moeller@pc02:~/public_html$ ls -l kmail_valgrind.log.*
-rw------- 1 moeller inb 64574 Mar 22 17:02 kmail_valgrind.log.29978
-rw------- 1 moeller inb 62473 Mar 22 17:08 kmail_valgrind.log.30233
moeller@pc02:~/public_html$ chmod go+r kmail_valgrind.log.*
moeller@pc02:~/public_html$ !ls      
ls -l kmail_valgrind.log.*
-rw-r--r-- 1 moeller inb 64574 Mar 22 17:02 kmail_valgrind.log.29978
-rw-r--r-- 1 moeller inb 62473 Mar 22 17:08 kmail_valgrind.log.30233

f*** - the log files are plain noise ;(
The only indication there seems to be is that the cache is touched in a fragile way - and that it's possibly timing related, as it works with valgrind. But at least you got a work around for the crash now ;)

Valgrind long here: http://cekirdek.pardus.org.tr/~ismail/tmp/kmail-valgrind.log

*** Bug 143785 has been marked as a duplicate of this bug. ***

*** Bug 144490 has been marked as a duplicate of this bug. ***

*** Bug 146555 has been marked as a duplicate of this bug. ***

*** Bug 157596 has been marked as a duplicate of this bug. ***

I am not sure whether Bug 157596 really is a duplicate of this bug. 
I did not have problems with other filters yet; just with virus filter clamav.  I will test whether I get problems with other filters or operations on a larger number of selected mails, too.   

*** Bug 162104 has been marked as a duplicate of this bug. ***

*** Bug 167358 has been marked as a duplicate of this bug. ***

*** Bug 173532 has been marked as a duplicate of this bug. ***

*** Bug 185691 has been marked as a duplicate of this bug. ***

Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding