Bug 1171480

Summary:	Gnome shell background logo extension causes high cpu usage
Product:	[Fedora] Fedora	Reporter:	Matt Spaulding <mspaulding06>
Component:	gnome-shell-extension-background-logo	Assignee:	Florian Müllner <fmuellner>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	21	CC:	chkr, dtrudg, enaut.w, fmuellner, kalevlember, nanopqr
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-05 14:27:10 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 Matt Spaulding 2014-12-07 15:56:09 UTC

Description of problem: Gnome shell cpu usage is high when the background logo extension is enabled.


Version-Release number of selected component (if applicable): 
3.14.0-1.fc21.noarch

How reproducible:
Always

Steps to Reproduce:
1. Enable the extension and see high cpu usage

Actual results:
CPU usage stays between 50% and 60%

Expected results:
No noticable difference in CPU usage

Additional info:

Comment 1 David Trudgian 2015-02-10 02:43:35 UTC

See also bug #1177683:

Confirmed on a macbook air 6,2.

if I disable the 'Background Logo' extension via https://extensions.gnome.org/local/ then the gnome-shell idle cpu usage drops to <1%.

I did some more digging, and noticed that I it seems to be an issue with certain logo files only, chosen from /usr/share/pixmaps via the extension's settings panel. E.g. the 'fedora-logo.svg' logos causes approx 50% CPU. The 'fedora-logo.png' PNG format logo has the same issue. However, if I choose 'fedora-logo-sprite.png' or 'fedora-logo-sprite.svg' I do not see the gnome-session idle CPU above 1%.

Comment 2 Christian Krause 2015-04-05 14:27:10 UTC


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