gnome-keyring chews CPU and disk for 40 seconds on chrome startup

Bug #1436640 reported by Dan Kegel
12
This bug affects 2 people
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
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
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)

Revision history for this message
Dan Kegel (dank) wrote :
Revision history for this message
Dan Kegel (dank) wrote :

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
   https://productforums.google.com/forum/#!topic/chrome/0nLjeCisf1A
and
  http://code.google.com/p/chromium/issues/detail?id=98601#c35
and
  https://src.chromium.org/svn/trunk/src/chrome/browser/password_manager/native_backend_gnome_x_unittest.cc
  https://src.chromium.org/svn/trunk/src/chrome/browser/password_manager/native_backend_gnome_x.cc

Evidently chrome uses gnome-keyring, and beats the crap out of it while syncing password stores with the cloud.

affects: gnome-keyring (Ubuntu) → chromium-browser (Ubuntu)
Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
assignee: nobody → Chad Miller (cmiller)
Revision history for this message
Dan Kegel (dank) wrote :

On a slower Ubuntu 14.10 system (AMD e-450) with chrome 39.0.2171.95, it takes longer (90 seconds of cpu?) to finish. A few seconds after the churning stops, I see:

$ ps augxw | grep keyr
dank 2103 32.7 0.6 384248 25184 ? SLl 13:32 1:28 /usr/bin/gnome-keyring-daemon --daemonize --login
dank 6019 0.0 0.0 13680 2104 pts/7 S+ 13:36 0:00 grep keyr

Revision history for this message
Olivier Tilloy (osomon) wrote :

That's an old issue.

Dan, are you still seeing it with recent versions of chromium?

Changed in chromium-browser (Ubuntu):
assignee: Chad Miller (cmiller) → nobody
status: New → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

This issue has sat incomplete for more than two years now without any response and didn't expire due to a bug watch. This bug report only refers to Ubuntu releases that are now "End of life" so I'm going to close this as "Invalid".

Please feel free to re-open this bug report if this is still an issue using a currently supported release of Ubuntu.

Changed in chromium-browser (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.