Bug 1171480 - Gnome shell background logo extension causes high cpu usage
Summary: Gnome shell background logo extension causes high cpu usage
Keywords:
Status: CLOSED DUPLICATE of bug 1177683
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell-extension-background-logo
Version: 21
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-07 15:56 UTC by Matt Spaulding
Modified: 2015-04-05 16:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-05 14:27:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.