| Summary: | Removing DIMAP Accounts from KMail crashes Kontact | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Daniel Buus <bugreporting> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | bugreporting |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
|
Description
Daniel Buus
2009-11-10 10:23:07 UTC
Created attachment 38223 [details]
Screenshot
Hmmm... Seems it left KMail in a somewhat half-configured state. At program start I am now presented with previous screen. Entering KMail Accounts settings, I see no trace of the deleted DIMAP accounts, but each time I exit settings I get several dialogs like, "Error opening /home/daniel/.kde/share/apps/kmail/dimap/1137026232; this folder is missing." that I have to click OK to. One directory remains in the dimap directory, totalling 84kB. Got rid of the dialogs by cleaning up kmailrc in ~/.kde/share/config/ - there was 120+ kB of crud in there, dating quite awhile back :) Glad it's fixed. As the backtrace is missing the debug symbols, I'll just close the bug with 'worksforme' (unless you want to reproduce it :)) Hi again :) Sorry for the late response - joined the übercool people who have the new improved flu ;) Also, sorry for being imprecise - what was fixed by my tampering with the rc file was simply the multitude of dialogs that would pop up again and again when using the program after the crash happened. So the OB, the crashing, is still, well, open or whatever :) Anyway, it happened again at home, where I did the same thing on my home laptop (removing two (actually the same two) DIMAP accounts for Google mails). Eventually went into dialog spasms, then crashed, then spammed me with dialogs on restart and periodically while using the program. I'm wondering if this has anything to do with the buggy way that big numbers of email is handled in KMail? For instance, when copying/moving many emails from one folder to another, I have to make sure not to copy too many at a time, or KMail will eat all available memory, then all the swap space, then moving the mouse becomes close to impossible, then KDE starts killing processes, then KDM goes down in flames. Actually, I previously thought that this was probably because KMail copied all source mails into memory before putting them into the target, but I just moved about 1000 mails from one IMAP account to another IMAP account (no local files), and within roughly 10 secs, KMail had eaten 64.5% of my 4GB memory, then started to do the moving. This cannot be because of copying the mails into memory, as they're on an IMAP server, so fetching them would take much longer than 10 secs... Also, while moving them, the memory usage slowly increased to just over 70%, then slowly decreased to 67.4% when it finished. Interesting, that was half an hour ago, and KMail has still not released the memory. This sounds like a bad memory leak, doesn't it? And would explain why KMail crashes so often when doing interval mail checks on my old DIMAP setup (my GMail has more than 20,000 messages). I actually turned off interval checks on DIMAP to avoid getting the stuttering-mouse-everybody-swapping-argh-konsole-killall-9-kontact-phew scenario :) Anyway, sorry, this is probably a completely different bug, should've filed it elsewhere, I'm just wondering if these are related... And probably there won't be any work on the mail data structures, since AFAIU, you're currently working on letting Akonadi do the storage now, right? Or maybe I'm just misinformed :) The growing memory when moving emails around is already reported: that's bug 185147. It will probably be fixed as soon as KMail uses akonadi (in KDE 4.5). For the current report: The backtrace is not helpful without the debug symbols. (the '?? () from /usr/lib/libkmailprivate.so.4' lines are useless). http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports has some informations about how to improve it. Roger! Thanks :) However, I can't reintroduce the bug, as in the meantime I've finished my email maintenance and no longer have the original files... I'm therefore marking it resolved. Thanks for your time, though :) Looking forward to the Akonadi-based new version! |