GNOME Bugzilla – Bug 310855
Evolution uses up all memory when formatting large plain text email.
Last modified: 2006-03-15 04:25:48 UTC
Steps to reproduce: 1. Select large email with single click and evolution eats up memory as quickly as the other programs are swapped out (I'd normally kill it by the time it reaches 70% of 700MB). The email in question is a plain text rsync output so it's larger than the average email (10MB) but still shouldn't 'crash' the mailer. Stack trace:
+ Trace 61851
Thread 1 (Thread 16384 (LWP 25114))
Other information:
Adam: I'm unable to reproduce this bug. I tried wiht Evolution 2.3.4 and gtkhtml 3.7.4. I tried an attachment with 38 MB and I don't face any such issues as stated in this bug. I tried rpm file as attachment. What type of attachment you tried ?
Thanks for the reply. Attachments are fine, it's when you actually try to display the contents that the problem arises. It turns out that it isn't a problem specific to the 10MB email, it's just a reflection of the heavy memory usage involved in displaying large emails. I used the following to generate various sized emails: cat /dev/urandom | uuencode -m - | grep -v base64 \ | dd bs=1k count=5000 |mail -s 5mb <email address> Here are the virtual sizes of evolution after startup and displaying 1 email: 1KB - 139MB 1MB - 181MB 3MB - 282MB 5MB - 392MB The memory also isn't freed after viewing a different email. I'm not sure how much memory is considered too much for this kind of thing. The version of gtkhtml I'm using is 3.6.2, I don't seem to have any newer versions listed using my preferred install system. Adam.
Shaheed / Subodh / Shilpa ? Hey guys can you regress this bug in IMAP / Groupwise / Exchange mailer ?
Needinfo.
*** Bug 318126 has been marked as a duplicate of this bug. ***
adding memory keyword
Due to the amount of spam I'm now getting to the address I used solely for submitting this bug report I'm no longer going to be collecting email destined for this address. Maybe you could prevent bugzilla from putting email addresses directly into the html whilst you are fixing this bug ;) Thanks, Adam.
*** Bug 325231 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 273171 ***