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 587923 - Sucking up huge amounts of memory, eventually running out of RAM and crashing
Sucking up huge amounts of memory, eventually running out of RAM and crashing
Status: RESOLVED OBSOLETE
Product: evolution-mapi
Classification: Applications
Component: miscellaneous
0.27.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2009-07-06 20:35 UTC by Matthew Barnes
Modified: 2010-03-31 04:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew Barnes 2009-07-06 20:35:38 UTC 
Forwarding this from a Fedora bug:
http://bugzilla.redhat.com/show_bug.cgi?id=509903


As described below, evolution with MAPI no longer crashing on startup, but now
sucking up huge amounts of memory and CPU, eventually running out of memory and
crashing.

Startup crash gone.  Now other issues.  Got it to crash twice after setting up
a MAPI account.  Unfortunately, can't replicate that crash with debuginfo
packages installed.  However, now evolution is consuming a huge amount of RAM
(1.5GB resident, >3GB total virtual size) and sucking a huge amount of CPU.  I
suspect that the previous two crashes were out-of-memory issues, since I just
got this:

Glib-ERROR **: gmim.c:175:failed to allocate 65536 bytes
aborting...

I'm pretty sure evolution shouldn't need >3GB of RAM just to read my email. 
Something is definitely still wrong here.
Comment 1 Akhil Laddha 2009-12-21 06:59:04 UTC 
similar bugs : bug 563952 , bug 575960
Comment 2 Akhil Laddha 2010-02-16 05:38:34 UTC 
libmapi 0.9 has many memory leak fixes. It will be great to know the feed back with libmapi 0.9 and 2.29.x / 2.28.x, thanks.
Comment 3 Akhil Laddha 2010-03-31 04:52:05 UTC 
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution-mapi (0.30.0), please reopen. thanks in advance.