Evolution 2.22.1 valgrind run with a nice amount of lost blocks

[C de-Avillez]

Binary package hint: evolution

Well... there I was, at the current contract, without access to email (they block everything). I had to prepare some emails and I had some free time.

So, I wondered, what about running Evo under valgrind for a while? And there I went. I decided to run just Evo under valgrind (next in line will be E-D-S), and did it for about 90 minutes. While I was writing my emails, Evo was busy trying to download -- and upload -- emails and, or course, failing miserably.

Anyway. When I finished writing the emails I stopped Evo and had a quick look at the valgrind log.

And... found a nice chunk of lost memory.

So, here it is. I thought of opening it straight in bugzilla, but decided that it was worth a LP bug. I will open bugzilla shortly.

Valgrind was run in a shell as follows:

#! /bin/bash
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log $*

and I called it as './valgrind.sh evolution --component=mail'.

[C de-Avillez (hggdh2)]

There is not much we can do here, so I am going out of SOP and setting the bug to triaged myself. If this is considered not kosher, please reset it as needed, and please warn me to never do it again.

[C de-Avillez (hggdh2)]

bug 219047 also has a nice valgrind log against evolution. I will add it to the upstream bug.

[Jörg Frings-Fürst (jff-de)]

change status to Fix released (see gnome-bugs)