Re: [Evolution] Anyone tried using Valgrind to find memory leaks in Evolution?

[Milan Crha <mcrha redhat com>]

On Mon, 2021-01-04 at 21:55 -0500, Jeff wrote:
> I don't know what to do next; that same command worked for Nautilus.
> Has anyone attempted this? Is there a better way?

        Hi,
one part of the preallocated memory can be a gigacage used by
WebKitGTK. It's better to disable it when running under valgrind. My
commands look like this:

   $ export GIGACAGE_ENABLED=0
   $ G_SLICE=always-malloc valgrind --show-leak-kinds=definite \
       --num-callers=30 --leak-check=full \
       --aspace-minaddr=0x100000000 evolution &>log.txt

Make sure you've installed debuginfo packages for glib2, gtk3,
evolution-data-server and evolution at least, to get usable backtraces.
        Bye,
        Milan