Red Hat Bugzilla – Bug 195252
Evolution hogs the CPU with the latest updates
Last modified: 2007-11-30 17:11:35 EST
Hi, after applying the latest evolution updates, Evolution won't work correctly
with my Exchange account. It was working fine before the updates.
Basically evolution will hang using 100% of the CPU when trying to watch an
email with attachments in the Exchange account. The funny thing is that it
doesn't block the GUI, I can use the menus, quit the application but it wont
show any mail after the block. This problem is triggered by mails with
attachments, I usually can read through my mails that doesn't have attachments
without any problem before triggering the bug.
There have been some discussion in this two forums posts:
And I reported the bug upstream:
In that bug report there are some backtraces and more information that could be
of relevance to fix this problem.
Looking at the forum posts and the b.g.o bug report, there are many people
seeing this problem.
Please... really... take a look at http://bugzilla.gnome.org/show_bug.cgi?id=344656
There have been a lot of findings in that bug report, maybe this is a Red Hat
specific bug and somebody here could give us a hand. There are a lot of people
suffering this problem and I refuse to go back to the old version without
resolving the issue first... even if evolution is a critical piece of my day to
Is there anyone looking at this problem?? There have been a lot of talk in the
upstream bug report:
Are you still seeing this behavior with evolution 2.6.3 and co.?
Have you been able to determine whether this is a Fedora-specific bug, or are
users of other distros are seeing this too? I have only skimmed through the
upstream bug reports.
The problem seems to go away when I upgraded to 2.6.3 (yum
--enablerepo=updates-testing update evolution-connector). Thanks!
William, can you confirm that the problem is fixed in evolution 2.6.3?
WFM too :) phew!
Based on comments here as well as in the upstream bug report, the consensus
seems to be that Evolution 2.6.3 fixes the excessive CPU usage. So I'm going to
close this bug, but please re-open it if you find that you are still seeing the