gnome-keyring chews CPU and disk for 40 seconds on chrome startup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
To reproduce:
0) start top
1) start chrome
2) watch disk light flash; watch cpu activity for gnome-keyring peg; notice gnome-keyring in D state; notice chrome and whole machine responding poorly
3) 40 seconds later, system returns to normal, and chrome beings responding quickly as expected.
This is ironic and annoying, since I never use gnome's keyring. Ever.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-keyring 3.10.1-1ubuntu4.1
ProcVersionSign
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 25 19:52:44 2015
InstallationDate: Installed on 2014-07-18 (251 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | gnome-keyring (Ubuntu) → chromium-browser (Ubuntu) |
Changed in chromium-browser (Ubuntu): | |
assignee: | nobody → Chad Miller (cmiller) |
dank@i5:~$ ls -l ~/.local/ share/keyrings/
insgesamt 564
-rw------- 1 dank dank 569425 Mar 25 19:51 login.keyring
-rw------- 1 dank dank 207 Jul 7 2013 user.keystore
See also /productforums. google. com/forum/ #!topic/ chrome/ 0nLjeCisf1A code.google. com/p/chromium/ issues/ detail? id=98601# c35 /src.chromium. org/svn/ trunk/src/ chrome/ browser/ password_ manager/ native_ backend_ gnome_x_ unittest. cc /src.chromium. org/svn/ trunk/src/ chrome/ browser/ password_ manager/ native_ backend_ gnome_x. cc
https:/
and
http://
and
https:/
https:/
Evidently chrome uses gnome-keyring, and beats the crap out of it while syncing password stores with the cloud.