After running the 'stopwatch' feature of gnome-clocks for awhile (>=50m), my system becomes extremely slow & unresponsive. The behavior seems indicative of thrashing/swapping, although performance slows to such a crawl that I can't open the 'Resources' tab of the system monitor to check the memory usage. One gnome-clocks is force quit, the system returns to its normal, snappy performance.
It would seem that gnome-clocks has a memory leak.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-clocks 0.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Wed Dec 19 15:27:14 2012
InstallationDate: Installed on 2012-11-05 (43 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-clocks
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time.