Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins

[EsAmo]

This is Ubuntu 14.04 LTS x64.

I removed good amount of remembered passwords but there are no noticable changes.

Chrome is v 40.0.2214.10 beta (64-bit)

---

Regards & respect.

[Launchpad Janitor (janitor)]

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

[Elliot Voris (elliotfriend)]

I'm using Chrome Version 41.0.2272.89 (64-bit). I'm running Linux Mint 17.1 Cinnamon

I went in and removed some of the many, many stored passwords in Menu > Preferences > Passwords and Keys

The ~/.local/share/keyrings/login.keyring file was 1018K before, and 765K after working through about one-third of the list of passwords. Starting up Chrome, I was asked to login again. After I did that, things appear to be working smoothly.

I'll update after some more extended use.

[EsAmo (esamokoram)]

Hmm, important thing I should mention is that I ciphered passwords by my own phrase not by Google default setting (Chrome preferences).

And that choking CPU is 2x 1700 MHz, one thread loaded by daemon is 1x 1700 MHz.

Regards & respect.

[EsAmo (esamokoram)]

Reinstalled `gnome-keyring` and upgraded Chrome to v42 beta. Load time seems decreased.

Regards & respect.

[owise1 (o-wise-1)]

I have noticed the same behaviour - after boot and starting chrome the gnome-keyring-daemon process takes about 50% of CPU for about 5mins.

[EsAmo (esamokoram)]

Well I had 50% load as well but there are two CPU threads so this is 100% of one. Clearly overloaded process. Have You tried my solution?

`gnome-keyring` has to be reinstalled from Synaptics and `Chrome` as well but installed from a package if beta.

Regards & respect.

[Bernhard Zürn (bernhard-zuern)]

I can reproduce the problem with chrome but i cannot reproduce it with chromium ... strange ...

[Scott Stensland (scottstensland)]

My system typically runs just fine even with ~/.local/share/keyrings/login.keyring over 1.3 mb with 5000+ lines,
however CPU goes over 75% only when I setup auto login without ubuntu password prompt on reboot.
I do get that keyring password prompt a few seconds after boot completes. Then CPU goes through the roof.
ubuntu 14.04 As a top-gap I am going back to the normal boot login password prompt

[Scott Stensland (scottstensland)]

This issue just happened to me again ubuntu 16.04 ... although not specific to that release as it happens on earlier releases too

 ... it was after changing my Google password
... I then needed to reboot for another reason
 ... after boot I then launched Chrome browser Version 50.0.2661.11 dev (64-bit) and then noticed very high CPU usage

 ... on Chrome browser top right of menubar was a yellow triangle
 ... I clicked it and was prompted to login to Google

 ... after this login the high CPU usage immediately stopped

[Petar Bojovic (petar-bojovic-paxy)]

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).

[Oleksandr Zahorulia (hast4656)]

Any news on this one? I still have this issue.

[Michael MacEachern (maceach-b)]

Affecting me on latest Chromium browser and Ubuntu Mate 16.04 on a raspberry Pi.

As if it was one more reason to go back to Firefox, this is possibly the final nail in the coffin.

[William Crandell (crandellws)]

My best solution is to use `gnome-keyring-daemon-old`