gnome-keyring use 100% CPU usage when Google Chrome started

gnome-keyring-daemon-use-100percent-cpu.mkd

gnome-keyring use 100% CPU usage when Google Chrome started

c.f.

• http://i.cmaas.net/pc/Linux/Wine/1368700507 (ja)
• https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/939301
• https://forums.ubuntulinux.jp/viewtopic.php?id=13910 (ja)

Environment

• OS: Knoppix 7.0.3 LCR
• DE: LXDE

Chrome

google-chrome-stable .deb package

chrome://version

Google Chrome	27.0.1453.110 (Official Build 202711) 
OS	Linux 
WebKit	537.36 (@151310)

Chrome Sync

• in use
• works well before touch gnome-keyring checkbox
• works well after KILL gnome-keyring processes

Sequence of events

What's the trigger? (prob gnome-keyring/libc SEGV)

start lxsession-edit in menu

open menu

check "SSH Key Agent" in "Automatically Started Applications" tab

Segmentation fault(SEGV)

SEGV in syslog

Jun 17 02:22:38 Microknoppix kernel: [ 8666.470367] lxsession-edit[8489]: segfault at bee8e454 ip b6c355bb sp bfaa0a80 error 4 in libc-2.13.so[b6bc7000+142000]

begin 100% CPU usage

when google-chrome started

htop hardcopy

  1  [||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||100.0%]     Tasks: 103, 181 thr; 3 running
  2  [|||||                                                         5.8%]     Load average: 3.85 2.39 1.64 
  Mem[||||||||||||||||||||||||||||||||||||||||||||||||||||||||571/3036MB]     Uptime: 10:24:57
  Swp[                                                          0/2277MB]

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command                                                                                   
 9839 knoppix    20   0 78976 37748  3816 R 100.  1.2  1:47.68 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets                   

uncheck "SSH Key Agent"

no error yet, so press "OK"

Segmentation fault(SEGV) again

OMG. SEGV in syslog

Jun 17 02:37:18 Microknoppix kernel: [ 9546.463089] lxsession-edit[8531]: segfault at bee746b4 ip b6c745bb sp bff2b930 error 4 in libc-2.13.so[b6c06000+142000]

keyring zombie

unchecked "SSH Key Agent", but actual keep auto-start. so CPU usage 100% everytime when Chrome started

WTH

---

Temporally calm down

do sudo kill -9 KEYRING_PROC [, PROC_NUM ...], stability is back

after kill keyrings

htop hardcopy

  1  [||||                                                          4.6%]     Tasks: 102, 171 thr; 1 running
  2  [||                                                            2.6%]     Load average: 1.99 0.82 0.78 
  Mem[|||||||||||||||||||||||||||||||||||||||||||||||||       570/3036MB]     Uptime: 07:24:43
  Swp[                                                          0/2277MB]

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command                                                                                   
 9839 knoppix    20   0 59712 18336  3812 D  0.0  0.6  0:27.17 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets                   

creepy...

---

packages / confs

gnome-keyring packages

knoppix@Microknoppix:~/.gnome2/keyrings$ aptitude versions gnome-keyring | grep -P '^i' -B 1 -A 2
Package gnome-keyring:
i   3.2.2-2                                                                 100 
p   3.4.1-5                                       stable,testing,unstable   990 
p   3.8.0-1                                       experimental              1   
--
Package libgnome-keyring-common:
i   3.4.1-1                                       stable,testing            990 
p   3.8.0-2                                       unstable                  500 

--
Package libgnome-keyring0:
i   3.4.1-1                                       stable,testing            990 
p   3.8.0-2                                       unstable                  500 

--
Package libpam-gnome-keyring:
i   3.4.1-4                                                                 100 
p   3.4.1-5                                       stable,testing,unstable   990 
p   3.8.0-1                                       experimental              1   
knoppix@Microknoppix:~/.gnome2/keyrings$ 

~/.gnome2/keyrings

knoppix@Microknoppix:~/.gnome2/keyrings$ ls -A
default  default.keyring

/etc/xdg/autostart

knoppix@Microknoppix:/etc/xdg/autostart$ ls -Al
total 40
-rw-r--r-- 1 root root 5070 Jan 26  2012 gnome-keyring-gpg.desktop
-rw-r--r-- 1 root root 6426 Jan 26  2012 gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root 6036 Jan 26  2012 gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root 4923 Jan 26  2012 gnome-keyring-ssh.desktop
-rw-r--r-- 1 root root 7018 Apr 28  2012 gsettings-data-convert.desktop
-rw-r--r-- 1 root root 4673 Mar 25  2012 nm-applet.desktop
-rw-r--r-- 1 root root  250 Sep  9  2011 notification-daemon.desktop
-rw-r--r-- 1 root root 4651 Nov 12  2011 polkit-gnome-authentication-agent-1.desktop
knoppix@Microknoppix:/etc/xdg/autostart$ 

knoppix@Microknoppix:/etc/xdg/autostart$ gview gnome-keyring-*
4 files to edit

:buffers
  1  h=  "gnome-keyring-gpg.desktop"    line 112
  2  h=  "gnome-keyring-pkcs11.desktop" line 116
  3 #h=  "gnome-keyring-secrets.desktop" line 115
  4 %a=  "gnome-keyring-ssh.desktop"    line 114
Press ENTER or type command to continue

Ugly fix:
Remove gnome-keyring execute privilege.

chmod -x /usr/bin/gnome-keyring-daemon

After this, gnome-keyring-daemon will not make any Chrome issue anymore, but it will not save any system password (google chrome password will be saved and you can used saved one too).

I also have this problem with Yandex Browser (Chromium clone).

Can't believe this is still an issue after several years!
Thanks Paxy, for for preventing an easy fix for this.

The fix is to install Chromium on Linux.
Then add the following to /etc/chromium.d/default-flags:

# Disable GNOME keyring (SLOW!)
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --password-store=basic"

This will also avoid gnome-keyring-daemon and use basic storage. :/ But fixes the 100% CPU and slow passwords issues.

If someone knows how to set the equivalent in Chrome then please ping me.

I still have this with Yandex-browser in Fedora-MATE. Filed a request to Yandex-browser support. I now suspect it may be related to system locales.

Yandex-browser support is usually very responsive to bugreports. But this particular report they seem to totally ingore. In the past I once filed another report on this that was also ignored.

Finally I again did -x to gnome-keyring-daemon. I thought it may cause browser not to remember passwords. But it seem to work well now without it. I don't know what problems and where it may cause in future.

Same issue with ubuntu 17.10 and any other ubuntu-based distro.

@DeadMate right on, I'm getting this with ubuntu 17.10 as well.

+1 here.
Debian 8 with Cinnamon.

Yandex-browser support answered to me weeks later, acknowledged the issue and said they'd be looking at it some time.

Same here (Ubuntu 16.04, Chrome beta 64). This seems the official thread : https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825?comments=all

I put this in a .sh file that runs in a chrome after updates :

sed -i 's/Exec=\/usr\/bin\/google-chrome-stable %U$/Exec=\/usr\/bin\/google-chrome-stable %U --password-store=basic/g' /usr/share/applications/google-chrome.desktop

sed -i 's/Exec=\/usr\/bin\/google-chrome-stable$/Exec=\/usr\/bin\/google-chrome-stable --password-store=basic/g' /usr/share/applications/google-chrome.desktop

Same issue

+1

I'm getting this too... can't believe it's not fixed by now.

+1

4 yrs and no fix :| !

I have this problem in 2019 and chrome 74

Fixed upstream https://gitlab.gnome.org/GNOME/gnome-keyring/merge_requests/5#note_339865

still happen
it happen in the middle of long coding session. so annoying

It is, @bokunodev, especially if you use 2.74 GLib.
That might be due to a GLib commit introduced 3 weeks ago, it has been fixed in 2.75.
https://gitlab.gnome.org/GNOME/glib/-/issues/2795