Comment 2 for bug 1743739

If this is reproducible and if your machine allows and if this still happens in 3.28, could you provide valgrind logs? Something like:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --num-callers=50 --tool=memcheck --leak-check=full --show-leak-kinds=definite --track-origins=yes evolution &>valgrindevolog.txt