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

List:       kmail-devel
Subject:    [Bug 110574] KMail crashed when opening a large message (eg. 80 Mb)
From:       <ferdinand () telegraafnet ! nl>
Date:       2005-08-15 14:31:06
Message-ID: 20050815143106.28488.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=110574         




------- Additional Comments From ferdinand telegraafnet nl  2005-08-15 16:31 -------
Hi Thiago,

> Unfortunately, that's a border case. KMail isn't allocating that memory all
> at once, which means it would have to watch its memory consumption. There's
> no way to tell what limit to impose...


True. There's no way to make a nice solution for this. Maybe a max memory or 
max message size setting is something.

By the way, why is a message of 80 Mb so large in memory ?

> As for being killed by the kernel, I am not sure this is the case. If it
> were, you wouldn't be seeing the Crash Handler dialog at all, and the
> signal would have been SIGKILL, not SIGSEGV.


If i enlarge my swapspace to 2Gb (my memory is 512Mb and my swap was 128Mb), 
the proces is growing till 1,5 Gb (with a 66Mb mail) and than it's stable. 
But nothing is responding anymore (swapspace on a laptop is not very 
vast :-)) so i still had to kill it my self.

About the Crash Handler dialog, sometimes it not shown. Most of the time it 
is.

> This still looks like a bug, but without a backtrace it is not easy to
> reproduce. Maybe I'll mail myself 80MB... is that 80MB body, or does it
> include attachments?


It's body text, with most lines not longer than 50 characters.
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel

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