Bug#775242: gnome-clocks: Uses ridiculous amount of CPU time for timer and stop watch
Andreas Bombe
aeb at debian.org
Tue Jan 13 00:21:52 UTC 2015
Package: gnome-clocks
Version: 3.14.1-1
Severity: minor
I found that the amount of CPU time gnome-clocks uses for rendering a
running stop watch or timer and even more what it causes Xorg and in a
smaller way gnome-shell to consume is simply way out of proportion.
The combined (gnome-clocks + Xorg + gnome-shell) CPU usage on this
laptop as reported by top goes over 50% (of one core, that is), same on
my desktop machine (intel and radeon graphics, respectively). This makes
it somewhat unsuitable to run on battery power.
Given the relatively simple graphic effects it displays, I would expect
much less resource consumption.
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-clocks depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1
ii geoclue-2.0 2.1.10-2
ii libatk1.0-0 2.14.0-1
ii libc6 2.19-13
ii libcairo-gobject2 1.14.0-2.1
ii libcairo2 1.14.0-2.1
ii libcanberra0 0.30-2.1
ii libgdk-pixbuf2.0-0 2.31.1-2+b1
ii libgeocode-glib0 3.14.0-1
ii libglib2.0-0 2.42.1-1
ii libgnome-desktop-3-10 3.14.1-1
ii libgtk-3-0 3.14.5-1
ii libgweather-3-6 3.14.1-1
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
gnome-clocks recommends no packages.
gnome-clocks suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list