Version: 1.5 (using KDE 3.1.0) Installed from: (3.0) Compiler: gcc version 2.95.4 20011002 (Debian prerelease) OS: Linux (i686) release 2.2.20 Don't knwo if it is related at all, but seem to get these more often when I first look at mail in the morning, and it may be that it is related to something being swapped out to cache in memory? (Wild guess) The previous version of kmail seemed to have resolved this, but latest debs from ~nolden for stable seem to have the bug again. Attached is the backtrace (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 5592)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x41306a59 in wait4 () from /lib/libc.so.6 #0 0x41306a59 in wait4 () from /lib/libc.so.6 #1 0x4137de48 in __check_rhosts_file () from /lib/libc.so.6 #2 0x411c9453 in waitpid () from /lib/libpthread.so.0 #3 0x409936ea in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x411c6f54 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x4128f6b8 in sigaction () from /lib/libc.so.6 #6 0x40199392 in khtml::Loader::servePendingRequests () from /usr/lib/libkhtml.so.4 #7 0x4019ba1f in khtml::Loader::qt_invoke () from /usr/lib/libkhtml.so.4 #8 0x40cc6ef9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x40f27a93 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #10 0x40cdc5b5 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #11 0x40ce1a63 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #12 0x40c74b53 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #13 0x40c74954 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #14 0x4093448a in KApplication::notify () from /usr/lib/libkdecore.so.4 #15 0x40c57383 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #16 0x40c3937c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #17 0x40c8631e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #18 0x40c8627b in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #19 0x40c74caa in QApplication::exec () from /usr/lib/libqt-mt.so.3 #20 0x08175fe2 in KDialog::marginHint () #21 0x4127f14f in __libc_start_main () from /lib/libc.so.6
Subject: Re: New: kmail crash on rendering email in html Please send the message as attachment to 53605@bugs.kde.org.
Will send the next one that causes a crash, however, it shoudl be noted that once it crasdes, and I restart the following time I may be able to read the email. I will send the next two messages that do that in case you can find some similiarity. As well, I should note that I just changed Xserver versions, and the thought was that it could be related to the Xserver-svga that I was using. Now that I am back to xfree86 (ie Version 4) we will see if the problem persists. Another note. During the crash, I noticed that something else has changed. Previously, when I encountered a crash, kmail came back up quite cleanly. Now, I find it has messages in the outbox, that are ghosts of previously sent messages, with absolutely no content. Could this be an index that isn't cleaning itself when messages get sent? It prevents mail from being sent until the outbox is purged of these ghosts.
Still crashing first thing in morning, when deleting my junk mail fast.. Trace this time is... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 7914)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x41306a59 in wait4 () from /lib/libc.so.6 #0 0x41306a59 in wait4 () from /lib/libc.so.6 #1 0x4137de48 in __check_rhosts_file () from /lib/libc.so.6 #2 0x411c9453 in waitpid () from /lib/libpthread.so.0 #3 0x409936ea in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x411c6f54 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x4128f6b8 in sigaction () from /lib/libc.so.6 #6 0x40199392 in khtml::Loader::servePendingRequests () from /usr/lib/libkhtml.so.4 #7 0x4019ba1f in khtml::Loader::qt_invoke () from /usr/lib/libkhtml.so.4 #8 0x40cc6ef9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x40f27a93 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #10 0x40cdc5b5 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #11 0x40ce1a63 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #12 0x40c74b53 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #13 0x40c74954 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #14 0x4093448a in KApplication::notify () from /usr/lib/libkdecore.so.4 #15 0x40c57383 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #16 0x40c3937c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #17 0x40c8631e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #18 0x40c8627b in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #19 0x40c74caa in QApplication::exec () from /usr/lib/libqt-mt.so.3 #20 0x08175fe2 in KDialog::marginHint () #21 0x4127f14f in __libc_start_main () from /lib/libc.so.6
Subject: Re: kmail crash on rendering email in html It seems to crash always in khtml which is used to render the emails. Can you probably compile at least kdelibs yourself (configured with --enable-debug=full for full debug information)? This would be very helpful. BTW, you should probably disable rendering of HTML for your inbox or for whatever folder you collect spam in.
*** Bug 53771 has been marked as a duplicate of this bug. ***
Okay, I doubt this will help you but I had it crash again this morning.. It is usually when cleaning up my junk mail, and hitting delete a few times rapidly on heavy graphic oriented Spam. It seems more like a timing thing somehow.. The messages are very large, so saved them, and attached
Created attachment 857 [details] First email in order, it made it to trash on delete As I mentioned, I hit delete, delete, rapidly for about 5 messages, the first message reached trash, the seond message didn't so assuming the crash came between trying to render the first message, hitting delete, and trying to render the second message. No problem viewing the messages individually after the crash/restart, so I knwo if it has anything to with content, just an obscure bug in timing.. Anything else I can add?
Created attachment 858 [details] Second Email in order The second message per above comment
*** Bug 53923 has been marked as a duplicate of this bug. ***
*** Bug 54454 has been marked as a duplicate of this bug. ***
Also see bug 54515 which describes a bug caused by the same khtml problem, and has a testcase to reproduce it.
*** Bug 54741 has been marked as a duplicate of this bug. ***
*** Bug 54555 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 54515 ***
Ummm.. does this really look like the same bug as 54515? The backtraces look like something else is going on, and no progress has been noted on either bug..
*** Bug 55588 has been marked as a duplicate of this bug. ***
Both backtraces (and all the backtraces from duplicate reports) contain khtml::Loader::servePendingRequests. So yes, this is the same bug as 54515 (which seems to have been fixed in the meantime).