gnome-keyring-daemon uses a lot of memory

[rewind]

1) The version and edition of Linux Mint and version of gnome-keyring:

$ cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.1
DISTRIB_CODENAME=rebecca
DISTRIB_DESCRIPTION="Linux Mint 17.1 Rebecca"

$ cinnamon --version
Cinnamon 2.4.7

$ dpkg -l gnome-keyring
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii gnome-keyring 3.10.1-1ubun amd64 GNOME keyring services (daemon an

2) How to reproduce it.

Start one or more gnome-terminal sessions connected to remote server by ssh and leave them open for at least half an hour or more, e.g. snippet from pstree:

|-gnome-terminal(404)-+-bash(463)
        | |-bash(4195)
        | |-bash(14698)---ssh(14759)
        | |-bash(16908)
        | |-bash(18025)
        | |-bash(19604)
        | |-bash(20717)---man(20779)---pager(20795)
        | |-bash(23307)
        | |-bash(23607)-+-less(24019)
        | | `-pstree(24018)

3) The result in an hour or more is gnome-kerying-daemon process is using almost 1/6 of all of the host memory:

$ ps -p 32051 -o pcpu,pmem,pid,comm
%CPU %MEM PID COMMAND
 1.1 15.8 32051 gnome-keyring-d

$ cat /proc/32051/cmdline
/usr/bin/gnome-keyring-daemon--daemonize--login

If freshly started it is using not more than 1MB or less.

4) The expected is to leave the session for days at a time without any need for gnome-keyring-daemon to be restarted.

5) The problem is reproducible always, just have to leave some terminals open for some time.

Some remarks:
- Tried to reproduce similar behaviour with Ubuntu 14.04 and 14.10 without success.
- The same issue was reproducible also in Linux Mint 17 Qiana. In fact the host was upgraded from Quiana to Rebecca some months ago.
- Logging out and log-in back resolves the issue as the keyring daemon is restarted.
- Attempting to restart just the process results in:
/usr/bin/gnome-keyring-daemon -r --daemonize
** Message: couldn't communicate with already running daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: Replacing daemon, using directory: /run/user/1000/keyring-PQyeQe
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-PQyeQe
SSH_AUTH_SOCK=/run/user/1000/keyring-PQyeQe/ssh
GPG_AGENT_INFO=/run/user/1000/keyring-PQyeQe/gpg:0:1
GNOME_KEYRING_PID=28477

Password unlock prompt opens for every gnome-terminal window or session opened.

[oraslaci (oraslaci)]

This issue also affects me on Ubuntu 14.04.
It seems to be linked to chromium browser's data sync.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[fabioxxxx (fabioxxxx)]

i don't use chrome data sync .

But i did notice when recovering stored passwords for some websites , gnome-keyring memory usage grows , by the end of the week it's close to 200MB... need to reboot or logoff every week.

3.13.0-65-generic
Ubuntu 14.04.3 LTS
ii gnome-keyring 3.10.1-1ubuntu4.2 amd64 GNOME keyring services (daemon and tools)
ii libgnome-keyring-common 3.8.0-2 all GNOME keyring services library - data files
ii libgnome-keyring0:amd64 3.8.0-2 amd64 GNOME keyring services library
ii libp11-kit-gnome-keyring:amd64 3.10.1-1ubuntu4.2 amd64 GNOME keyring module for the PKCS#11 module loading library
ii libpam-gnome-keyring:amd64 3.10.1-1ubuntu4.2 amd64 PAM module to unlock the GNOME keyring upon login
ii python-gnomekeyring 2.32.0+dfsg-3 amd64 Python bindings for the GNOME keyring library
ii google-chrome-stable 45.0.2454.101-1 amd64 The web browser from Google

[Mark Drummond (dmark)]

Same issue on Mint 18.1 Cinnamon, htop says gnome-keyring is using 21.4% of my 16GB.

[James Niland (nilandsplace)]

This is for Ubuntu-gnome
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"
that also uses gnome shell although I am not sure why as it seems it does not work either
Both Opera browser and any version of Chrome or google-chrome demand it. However at start just below gnome-panel it is the second highest use of memory at startup. Currently sitting at over 32Mb real and 384 virtual memory. There is only one login is [Passwords and Keys]. Others seem unhappy with 1mb of ram, I however wish I could get it this low.
/usr/bin/gnome-keyring-daemon --daemonize --login is the command loaded.
Version gnome-keyring 3.10.1-1ubuntu4.3
Killing the process my system is entirely more responsive