Dear Steve Langasek,
> Brian, can you confirm that the SRUed version fixes the problem for you?
> We need some confirmation of the bugfix before it can be published to
> precise-updates.
>
> As Seb pointed out earlier, this problem is not reproducible for all
> users. By that measure, the test case in the bug description is
> incomplete, because it does not tell users how to reproduce the problem.
I have installed the SRUed version at home (at least, I think I did it
correctly):
ii gnome-keyring 3.2.2-2ubuntu4 GNOME keyring services (daemon and
tools)
It is running normally and not causing any problems at this moment.
Memory usage seems relatively normal:
hein 1899 0.0 0.0 368880 3732 ? Sl 21:01 0:00
/usr/bin/gnome-keyring-daemon --daemonize --login
although the virtual use does seem high but I see that with a lot of
programs on 64 bit ubuntu. I will try it out at work where I actually
noticed the memory leak and confirm again once I see it running a bit
longer.
Kind regards,
Hein
--
Hein Zelle h...@icce.rug.nl
http://www.icce.rug.nl/~hein
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
gnome-keyring-daemon leaks memory
Status in GNOME keyring services:
Fix Released
Status in “gnome-keyring” package in Ubuntu:
Fix Released
Status in “gnome-keyring” source package in Precise:
Fix Committed
Bug description:
* Impact:
gnome-keyring leaks memory which is not nice
* Test Case:
run a GNOME or Unity session for some time, watch the gnome-keyring-daemon
memory usage
* Regression Potential:
check that keyring keeps working fine (ssh/ggp agents, network-manager
passwords, etc)
-----------
gnome-keyring-daemon gets killed here every few days due to it's memory size
exceeding the site imposed limit of 2GB per process. The ulimit of course is
not the problem as even with an unlimited setting, it would just grow until it
was killed by the OOM killer.
The real problem here is that gnome-keyring-daemon has no business
growing to even a fraction of the 2GB limit imposed here. 2G for a
simple keyring daemon is absurd.
Looking at the upstream changelog for versions beyond the 3.2.2 on
which the Ubuntu version is based appear to have fixed memory leaks.
Given that this leaking 3.2.2-2ubuntu4 version is in the Precise LTS
release, upgrading to a newer Ubuntu release is not a solution nor an
option -- this LTS release is supposed to be supported beyond 2017. A
fix needs to be backported. Having gnome-keyring-daemon leaking for 5
more years is simply unacceptable.
ProblemType: Bug
DistroRelease: LinuxMint 12
Package: gnome-keyring 3.2.2-2ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
ApportVersion: 2.0.1-0ubuntu15
Architecture: i386
Date: Sat Dec 29 11:38:45 2012
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: [modified]
modified.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: [modified]
modified.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop: [modified]
modified.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop: [modified]
mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop:
2012-03-21T15:31:45
mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop:
2012-02-23T18:28:50
mtime.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop:
2012-02-23T18:26:38
mtime.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop:
2012-03-21T15:32:22
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-keyring/+bug/1094496/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
