[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 110574] KMail crashed when opening a large message (eg. 80 Mb)
From:       Chris Gebhardt <dev () openserve ! org>
Date:       2006-02-02 2:27:16
Message-ID: 20060202022716.8273.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=110574         




------- Additional Comments From dev openserve org  2006-02-02 03:27 -------
This is a very serious issue that needs more attention.  KMail is evidently using \
some terribly inefficient data structure for message bodies.  Though it may not \
result in an OOM crash on most machines, even text message bodies of around 0.5-2 Mb \
can trigger bad behavior in the form of run-away resource usage and memory leaks.  \
This behavior can be observed *any* time Kmail touches a large message body.  \
(preview pane, composer, view source, etc.)  The transport doesn't matter.  Behavior \
is identical with mbox,maildir,imap,etc.

Here's a real-world example viewing a 2Mb text message (a cron job report):

At Kmail load time with 3 IMAP accounts:  86M VSZ, 31M RSS
View large message:  136M VSZ, 77M RSS
View large msg. source:  148M VSZ, 91M RSS

The UI blocks and kmail process CPU usage is maxed while the message is loading, even \
on subsequent views. (takes about 10-15s on an AMD64 3000 w/1Gb)

Now close, de-select or even delete the large message.  Memory usage does not drop at \
all, hence evidence of a leak.

Also, try pasting a large (1-4 Mb) text into composer.  Similar results will be \
observed.  After the paste finally completes, any time you attempt to scroll the text \
in composer, kmail will hang for quite some time with maxed CPU usage.

This bug is possibly also related in its root cause to the following:
88427, 95060, 107649, 110574, 119281


[prev in list] [next in list] [prev in thread] [next in thread]