Comment 14 for bug 305428

I also used to have the problem -- see upstream report.

Since the update in intrepid, a couple of days ago, to evolution (et al) 2.24.3) the problem mysteriously disappeared -- or at least Evolution memory stays stable after a few hours of use.