Evolution-exchange uses 100% CPU

Bug #110073 reported by Maiko Herajin
10
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: evolution-exchange

When I start a new message in Evolution - even if I immediately close the new window - the process evolution-exchange starts to pick up in cpu usage, until it is nearly constantly consuming 100%. This goes on for as long as I let the program stay open. As soon as I close Evolution, the process goes away and all CPU usage returns to normal.

I am using Evolution on a corporate exchange server, running under Kubuntu Feisty Fawn. Thank you.

Revision history for this message
Maiko Herajin (maikoherajin) wrote :

As an aside, the same behavior is evident if I create a calendar event as well.

Revision history for this message
Guido Conaldi (guido-conaldi) wrote :

I can confirm the issue on my ubuntu 8.04 64bit. The same happens also if you are only adding a calendar event on your local calendar, as long as you have an exchange account configured.

Revision history for this message
Andy Kniss (akniss) wrote :

This happens to me as well on Ubuntu 8.04 amd64 using Evolution for Exchange mail. The only difference is that it constantly uses 50% of my cpu as soon as I start a new message. I've attached a screenshot showing my CPU usage.
Details of the Screenshot: Between 60s and 40s, Evolution is running. At 40s, I've started a new email message. At 30s, I closed the new email message, but the CPU usage is remains very high. I shutdown Evolution at about 10s, and the CPU usage returns to normal.

Revision history for this message
Zinn (l-zbikowski) wrote :

The same thing - but 30-40% cpu... Few minutes after turning on evolution....

Revision history for this message
DavidL (dlandis) wrote :

This didn't happen before I upgraded to Hardy. Now Evolution is fine *until* I begin to compose a new message. Then CPU shoots up and doesn't go down until I close Evolution as a whole, not just the new message window. I use evolution for exchange mail.

Revision history for this message
altery (yves-alter) wrote :

I experience the same behavior as DavidL and Andy Kniss:

As soon as I start composing a new message, the CPU usage of gnome-keyring-daemon goes up to 50% (on dual core CPU) and doesn't go down until I exit Evolution. I use Evolution with Exchange and IMAP accounts.

I'm under Hardy 64bit.

Revision history for this message
Jouke74 (hottenga) wrote :

Ubuntu Hardy 8.04 AMD64 version.

Same here as well. I also use evolution exchange for my work email account. As soon as I start typing a new message, one core of my 4200 X2 CPU goes to 100%. It also starts when you try to compose an email from another program, e.g. Openoffice Word or Firefox. The way to get it back to normal then is to start and close Evolution itself.

Revision history for this message
Matej Kenda (matejken) wrote :

I can confirm the same behaviour as well on laptop HP Compaq 6710b (Centrino Duo).

This behaviour started immediatelly after adding an Exchange account to Evolution.

Hardy, amd64.

Revision history for this message
Matej Kenda (matejken) wrote :
Revision history for this message
altery (yves-alter) wrote :

Specifying a GAL Server did indeed resolve the symptom of high CPU usage. Thank you.

Revision history for this message
Matej Kenda (matejken) wrote :
Revision history for this message
fig_wright (fig-wright) wrote :

This may be because Evolution is attempting to connect to LDAP servers or remote addressbooks/contacts, especially if you use a VPN to connect to mail. I notice that if I dont have my VPN open (i.e. I am using only my local mail) then cpu goes to 100%.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta?

Changed in evolution-exchange:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evolution-exchange:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.