Summary: | Freezes when reading large mail | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Nicola Döbelin <ndoebelin> |
Component: | messageviewer | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | wishlist | CC: | bjoern, cwehrmann, luigi.toscano, xavier |
Priority: | NOR | ||
Version: | 1.10.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Nicola Döbelin
2008-07-29 08:27:01 UTC
As a workaround, you can define a filter to move the message in another folder. Then you can open the file in your ~/kde(4)/share/apps/kmail folder using a text editor. kmail 1.11.0 Clicking on a stray 36MB message (in a maildir folder) caused a 500MB spike in memory consumption causing the host to swap and kmail to hang. After an hour the UI (menus, buttons, message-list) returned, but the message was not displayed in the preview. Double clicking the message resulted in hang that was eventually aborted by the user. I would suggest: * kmail reads a screenful of data for initial rendering before parsing full mail. (updates to the attachment lists seem acceptable) * kmail already looks up the message size for the hover distraction and might use this information based on some threshold to suggest to the user save the message for viewing in an editor or delete without being opened. * kmail detects if it's interactive UI becomes comatose for too long and stops whatever it is that it's doing. I realize this is non-trivial in a multi-tasking environment. Perhaps the previewer thread could just timeout after 5s and just prompt for action if the parsing hasn't completed. Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding. Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2. |