Comment 39 for bug 1633319

I had the same problem. Sunk over a day into trying to figure it out. I'm taking no chances: I removed evolution. I might reinstall it sometime when I am no under such a crunch.

What I find really frustrating is that I would expect the OOM (Out of Memory) killer to recognize that the process had consumed 14 GBytes of virtual memory and kill it, but it didn't. I would argue that if a user space process that can bring a system to its knees, then there is something else wrong with the system. I don't know enough about kernel internals to put my finger on it, and I am in a bit of time crunch right now.