evolution can't sign email after running for a long time

Thanks for your bug. Could you run "top" when that happens and note how much mem is free on your box and used by evolution task?

It happened again... Luckily I had set up a cron job to run every 5 minutes to log this stuff, because I tried opening up a console and it locked up entirely.

I attached the output as it is quite lengthy.

I should note that the system gets unresponsive and requires I reset the power if Evolution is left open very long. I have been closing Evolution down periodically, and this behaviour has disappeared (but not a solution). See the attached log file from my last note, and you can see that when left running, Evolution gets very memory intensive, so much to the point that all of my RAM and swap are used and I can't even do anything on my system - not even close Evolution to try and free up the memory.

Am I the only one who can replicate this behaviour?

Maybe you could install evolution-dbg evolution-data-server-dbg and try to figure what happens using valgrind? Those leak bugs are not easy to debug without a log and it doesn't happen for me by example. To use valgrind you just have to install the package with that name and run "valgrind --trace-children=yes --log-file=valgrind.log evolution". That makes the application really slow but is useful to know where the leak happens exactly

Do you still have the problem with Edgy or Dapper?

I have been turning off my PC nightly during the summer because it throws too much heat. I will try and check this soon. I am going to install Edgy very soon at home (already using it at work). If you want to close this bug, I can always open a new one later on, or if possible to reopen this one, if the issue persists.

Thanks a lot. Please reopen the bug once you have more information at hand.