evolution-data-server eats RAM

[Mark Duncan]

Binary package hint: evolution-data-server

Running Ubuntu Hardy amd64 with Evolution 2.22.1-0ubuntu2 installed. I am trying to connect the address book to my office's Active Directory server (LDAP) and I have these settings:

Name: AEC
Server: 192.168.0.4
Port: 389
Use secure connection: TLS encryption (I've also tried no encryption)
Login method: Using email address
Login: (my email address)

When attempting to browse the address book, I am prompted for my password. After inputting my password, the address book stays empty and attempting to search for anything returns nothings (not even an error) so it is unclear whether it is actually connecting or not. The problem is that after searching, evolution-data-server starts eating RAM at a rate of about 1-2MB per second. I found this when I stepped away from my computer for a while and returned only to have it moving extremely slow (took a whole minute for the screen saver to go away). Checking the system monitor showed that evolution-data-server was using 441MB of RAM.

Using both TLS encryption and no encryption causes evolution-data-server to start using up RAM after a search in my address book. SSL encryption would tell me that it could not connect, but that was expected since we don't use SSL on Active Directory here. evolution-data-server's RAM usage usually stays steady between 2 and 3 MB, but as soon as I press "enter" to search for a contact, it starts to climb and doesn't stop. It would be nice if someone could look in to this.

[C de-Avillez (hggdh2)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Mark Duncan (eattheapple)]

OK, I made sure evolution-data-server wasn't running and then ran Evolution with Valgrind. This is the first time I've used Valgrind so I hope it caught memory usage from evolution-data-server as well (since it was spawned by Evolution). I started evolution at 8:26am and evolution-data-server was using 1.4MB. I went to the address book and was prompted for my password. I put in my password and evolution-data-server started climbing right away (no search was necessary). It was climbing a lot slower than before I'm assuming because of Valgrind. I went to a meeting while it climbed and came back at 8:56am. evolution-data-server was at 100.8MB so I stopped it and gzip'd the log. The log is attached. If you need anything else, just let me know.

[Mark Duncan (eattheapple)]

Just after I posted that, my update notifier popped up. Seems like evolution has been updated to 2.22.1-0ubuntu2. I just finished updating and the bug is still present.

[C de-Avillez (hggdh2)]

Hello Mark,

Thank you for the Valgrind log. Although it is useful -- it does show a series of lost memory areas --, it will not help us on the E-D-S issue... Valgrind only looked at Evolution, not E-D-S.

For you to get valgrind against E-D-S, you have to:

1. stop all of Evolution: on a terminal under your X session, issue 'evolution --force-shutdown'
2. start valgrind against E-D-S: on a terminal under your X session, issue something like 'G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/evolution/evolution-data-server-2.22'
3. Run Evo normally. As you probably noticed, it *will* be slower, quite so.

Then do whatever you need to do to have it acquire memory (go to address book, etc).

The current valgrind run is still usable, and I will attach it to another upstream bug that deals with Evolution memory usage (bug 215925). But... we really need the valgrind run against E-D-S.

Thank you.

[C de-Avillez (hggdh2)]

Oops... forgot: please install the debug packages for Evolution, E-D-S & associated libraries *before* running valgrind again. Thanks.

[Mark Duncan (eattheapple)]

I was afraid the original log wouldn't have EDS data. Oh well.. at least it may be helpful for something else. I followed your instructions and now have a new valgrind log. I only let Evolution/EDS run for about 5 minutes (up until memcheck reached 100MB of RAM usage). Let me know if this one is good or not or if you need anything else.

[C de-Avillez (hggdh2)]

Mark, I am sorry, but I got extremely busy earning a life, and could not follow up here.

Your valgrind log is good, but before I send it upstream I would like to know if you are now running 2.22.2 (we just promoted it to hardy-updates). The reason is some leakages have been corrected...

Thank you and, again, sorry.

[Sebastien Bacher (seb128)]

do you still get this issue?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.