Ubuntu
evolution-data-server package

  1. Bug #219047
  2. Comment #4

Comment 4 for bug 219047

Revision history for this message
C de-Avillez (hggdh2) wrote :

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.