GNOME Bugzilla – Bug 322698
evolution/evolution data server extremely memory hungry/leaking
Last modified: 2008-06-19 12:53:06 UTC
Using evolution daily it keeps growing in memory usage... finally requiring each >300MB (that is e-d-s and evo) ... as a result it often gets killed by the kernel (although the machine as 1GB of mem) I also notice that the xorg process requires >500MB when playing with evo for some days... requiring restarts
adding memory keyword. well, generally complaining about the used memory is okay, but please tell us how this bug could be closed/solved (and don't say: hey, it's easy, just improve the code quality). :-) it's mostly uselesss to keep such bug reports open, because they are just too generally. if you like to, you can do a search in bugzilla for evo/e-d-s bugs containing the keywords "perf" and/or "memory".
Well the problem is that I am not doing anything particularly advanced stuff. I just read email over imap (polling every 2 minutes) from time to time switch to addressbook and calendar ... So I am not sure how I could help here. If I was on x86 I could give valgrind runs as feedback but as this is ppc I cannot. And yes this happens regularly (depending on evolution usage I have to kill evo every 1-7 days) just because evo eats ~400MB, e-d-s ~200MB ...
Stack traces of evolution and eds can be attached when memory hog reaches above 200mb ?. Approximatly how many folders are there in imap and how many mails in them ? How many contacts are there in addressbook. Could you try to use evolution 2.6.2 and update if this bug is still existing bcoz quiet a lot of memory leaks has been fixed in 2.6.2.
Less than <300 contacts, <30 email folders (IMAP) with in total <10000 mails. well at the moment it is at about 190M/ e-d-s at about 130M, but it is not running for long...
Most of the eds memory leaks has been fixed in 2.22. Can you please try ? Please refer bug 510949 for more information, thanks.
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 (2.22.x or later), please reopen. thanks in advance.