Comment 0 for bug 1092316
Revision history for this message
| tdeering (tomdeering7) wrote Using Stopwatch, System Becomes Slow & Unresponsive | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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. What I am observing seems to be thrashing, as an eventual result.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-clocks 0.1.4-0ubuntu1
ProcVersionSign
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
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-clocks
UpgradeStatus: No upgrade log present (probably fresh install)