This problem is very real. Please reopen.
I'm running evo 2.24 on Intrepid on a HP NW8440. I have the above symptoms daily.
I've attached valgrind output, generated thus: $ evolution --force-shutdown $ sleep 3 $ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=/home/rkh/evo-valgrind/2008-11-13-14:30:09.valgrind evolution --component=mail
I've not used valgrind and am unsure that this completed correctly. In my case evo RSS goes to 1.8G or so, then is killed. I don't know whether the valgrind output is complete in such cases.
-Reece
This problem is very real. Please reopen.
I'm running evo 2.24 on Intrepid on a HP NW8440. I have the above symptoms daily.
I've attached valgrind output, generated thus: always- malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file= /home/rkh/ evo-valgrind/ 2008-11- 13-14:30: 09.valgrind evolution --component=mail
$ evolution --force-shutdown
$ sleep 3
$ G_SLICE=
I've not used valgrind and am unsure that this completed correctly. In my case evo RSS goes to 1.8G or so, then is killed. I don't know whether the valgrind output is complete in such cases.
-Reece