Version: (using KDE KDE 3.2.92) Installed from: Compiled From Sources Compiler: gcc 3.3.4 (Debian 1:3.3.4-3) OS: Linux It took me about an hour with kmail eating 100% CPU to move 1042 mails from an online imap folder to an mbox on a local disk. KMail created tons of Jobs which could be seen in the joblist. It took few seconds to complete a single job and remove it from the joblist. While moving, the UI was still usable, although it was very sluggish. KMail ate a lot of RAM: ~ 92 MB RSS. A restarted KMail eats about 42 MB RSS here. The server or network connection is not the problem, KMail from KDE 3.2 did the same job under same conditions in a few minutes.
Daniel, as discussed on irc, the problem is that KMail merrily creates a progress item for each mail that needs to be downloaded, which for 1000 mails produces one bugger of a progress dialog, which takes a bit to initialize and burns some cpu. Once the dialog is filled, it starts to work through them at normal speed, as far as I can tell, at about 1 message per second with my DSL connection. I agree this case needs to be handled bette, but I'll postpone that until after the 3.3 release.
*** Bug 90285 has been marked as a duplicate of this bug. ***
I can't reproduce this on trunk r855160 however I don't have a folder with that many mail messages (only around 200). Downloading the mails on an IMAP account is pretty snappy though.
Still can't reproduce on 1.10.1.