desktop-packages team mailing list archive

[fabioxxxx <1094496@xxxxxxxxxxxxxxxxxx>]

Tested with chrome making the login on X website with my credentials saved,  gnome-keyring memory rose , logout and login on the same X website keyring memory rose again... by the end of the week gnome-keyring is using almost 200mb : O
(a lot of sites and ecomerce have timed logins so it happens a lot )

will the fix get to ubuntu 14.04  ?

UBUNTU 14.04.03  3.13.0-67-generic
google-chrome-stable                        46.0.2490.80-1
gnome-keyring                               3.10.1-1ubuntu4.2
Xfce 4.12

thanks.

-- 
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:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Precise:
  Fix Released

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