Comment 3 for bug 236171

I am including stack trace from my system, a Dell Latitude D630 with dual core, 2GB RAM, and 120 GB disk. I am running evolution on hardy against Microsoft Exchange. The 100% CPU occurs when composing a new message. Simply click the new message button and the CPU spikes at 100% and never returns to normal until evolution is closed. I don't have a non-exchange connected evolution to test the exchange-only theory. I only use evolution to solve the exchange client problem on linux. Exchange-storage may also be implicated, as I saw it consuming significant amounts of CPU along with the aforementioned gnome-keyring-daemon and evoluation itself. This bug renders evolution effectively useless when talking to exchange servers.