Bug 908515

Summary:	evolution high cpu usage due to the status bar
Product:	[Fedora] Fedora	Reporter:	Davide Repetto <red>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	lucilanga, mbarnes, mcrha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-07 08:00:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Davide Repetto 2013-02-06 21:55:03 UTC

Description of problem:
=======================
I've seen a bunch of bugs about opera and high CPU usage. Like Bug 841443, Bug 863164, Bug 836740. And I suspect many of these may be caused by Evolution frantically updating the status bar as in this case.

I'm quite positive that this is the culprit because disabling the status bar brings things back to normal.

Otherwise any operation that displays its progress on the status bar suddenly becomes extremely slow and as new "tasks" eventually accumulate on the bar, the whole system slows down to a creep.

You may not notice the problem if you have only one or two POP accounts and just a few mails, but it becomes quickly evident if you have a more loaded system like mine.


Version-Release number of selected component (if applicable):
=============================================================
evolution-3.6.3-2.fc18.i686


How reproducible:
=================
Enable the status bar and do anything that would display its progress in the bar. (eg. checking a folder, reading mail, etc)
CPU will spike to 100% ant everything will be much slower.

Comment 1 Milan Crha 2013-02-07 08:00:00 UTC

Thanks for a bug report. I think you see both bug #886239 and the hight CPU being caused by a gtk+ regression in 3.6.x with GtkSpinner animation, which is logged at [1]. Another related upstream bug can be [2]. I'm marking this as a duplicate of the above mentioned bug. Feel free to join the other upstream bugs.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=684639
[2] https://bugzilla.gnome.org/show_bug.cgi?id=683867

*** This bug has been marked as a duplicate of bug 886239 ***