Version: 1.11.0 (using KDE 4.2.0) OS: Linux Installed from: Fedora RPMs Here is exactly what I was doing. I was accepting Exchange calender invites, but clicking cancel in response to sending the accepted e-mail. I didn't associate these actions with kmail becoming sluggish, eatting ~180M of RAM, only ~30M of which was shared, until I killed the kmail thread, as quitting the application didn't actually close it, and restarted it. When it restarted, all of those "accepted" e-mail's I had cancelled popped up. After I went through and closed out each e-mail, kmail ran fine and has been running fine since. I have not tested these reproduction steps, but based on what I experience, I believe this would reproduce it. 1. Set-up kmail to not automatically send outgoing e-mail. 2. Create a bunch of e-mails, but when kmail pop's up the send now/later/cancel dialog, choose cancel. 3. KMail should become sluggish and use a lot more RAM then normal. 4. Restart kmail, should require kmail to be killed.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.