Bug 153885 - IMAP KIO process dies (due to trailing nulls?)
Summary: IMAP KIO process dies (due to trailing nulls?)
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: SVN trunk (KDE 4)
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-12 06:31 UTC by Josh Berry
Modified: 2008-02-06 18:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Berry 2007-12-12 06:31:52 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.2 
OS:                Linux

When KMail tries to list the messages in my inbox, it fails and pops up a dialog saying that the process for imap://localhost/ (my IMAP "server") has closed unexpectedly.

There are no messages in my xsession-errors to indicate what went wrong.

However -- and this is just a guess -- I did notice that KMail was going through and systematically marking all my messages as "Unread" (I'll try to isolate that bug later -- for now it's useful).

I checked the message it stopped on, and found a bunch of "=00"s at the end of the message.  This leads me to believe that kio_imap is choking on unexpected NULLs.  (Unfortunately I can't provide the message itself as it contains private information.)

Any suggestions for isolating this further?
Comment 1 Thomas McGuire 2007-12-15 18:18:56 UTC
See also bug 152652 (about the unread problem).
Comment 2 Mischael Schill 2008-02-05 18:37:44 UTC
I confim this on my citadel server. But no messages with =00 at the end..
Comment 3 Mischael Schill 2008-02-05 19:02:03 UTC
I think, this could occur if you switch fast between non-cached (is there a cache?) mails and too many connections are made. My server is pretty slow and probably doesn't respond quick enough. I look into it.
Comment 4 Mischael Schill 2008-02-05 19:08:53 UTC
Ah, something i forgot: In my case, kmail doesn't always crash after the dialog and i can use it further. It restarts the ioslave (so that it can crash on some other mail ;)).
Comment 5 Mischael Schill 2008-02-05 21:53:18 UTC
My investigation status:
The ioslave dies because of an out of bounds access to a qbytearray:
ASSERT: "i < uint(size())" in file /usr/include/QtCore/qbytearray.h, line 351

After I attached gdb to the ioslave, i couldn't reproduce the bug anymore. So this means hard work :(.

I think crashing of kmail is bug #154041.
Comment 6 Allen Winter 2008-02-06 18:45:16 UTC
SVN commit 771672 by winterz:

Mischael's fix for "IMAP KIO process dies (due to trailing nulls?)"
BUG: 153885


 M  +7 -4      imapinfo.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=771672