After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 318126 - 19 MByte text message exhausts virtual memeory
19 MByte text message exhausts virtual memeory
Status: RESOLVED DUPLICATE of bug 310855
Product: GtkHtml
Classification: Other
Component: Rendering
3.7.x
Other All
: High critical
: ---
Assigned To: gtkhtml-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-10-06 15:17 UTC by Stephen P. Schaefer
Modified: 2005-10-24 05:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Stephen P. Schaefer 2005-10-06 15:17:22 UTC
Steps to reproduce:
1. Do rpm -qal | mail me; on an "install everything" Fedora Core 4 host,
generating a 19Mbyte text e-mail message.
2. Attempt to view last lines of message with evolution.
3. Evolution process size balloons to > 1 Gbyte.  After an hour, the evolution
display still hasn't refreshed.


Stack trace:
This is more serious than "normal", but perhaps not technically "crashed".  No
stack trace generated.



Other information:
Recovery procedure:

evolution --force-shutdown

use some other mail client to process the e-mail, removing it from mailboxes of
which evolution is aware, e.g., use /bin/mail to save the message.

restart evolution
Comment 1 parthasarathi susarla 2005-10-06 16:00:34 UTC
Hi stephan, Thanks for the bug report. A lot of fixes w.r.t both evolution and
gtkhtml (for memory leaks) have gone in Evo 2.4.x and the latest gtkhtml. 

i tried doing the same thing on my machine, and i could render a 22 MB file
within a couple of minutes. Although i noticed that it used up around 911Megs of
my virtual and 790 megs of my resident memory. 

Upgrading might really let you be able to view the message, but still wud
exhaust memory.
Comment 2 André Klapper 2005-10-06 18:16:49 UTC
adding keywords
Comment 3 Kaushal Kumar 2005-10-24 05:47:25 UTC

*** This bug has been marked as a duplicate of 310855 ***