Comment 9 for bug 1169694

Likewise, buggy buggy evolution...

If you want to use the program, a workaround might be starting from a terminal with:

G_SLICE=always-malloc evolution

Its a bandaid, but if it works, the cause might be somewhere in evolution (or one of its many libraries) calling g_free() on memory acquired with the g_slice mechanism.

Finding it might be like looking for a needle in a haystack though!

Another possibility, valgrind is showing some use-after free invalid reads in webkit's renderer. These might be causing issues.