After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 624254 - gnome-keyring-daemon consumes ~100% on both cores.
gnome-keyring-daemon consumes ~100% on both cores.
Status: RESOLVED FIXED
Product: gnome-keyring
Classification: Core
Component: general
2.31.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-07-13 14:30 UTC by Maciej (Matthew) Piechotka
Modified: 2010-09-12 02:40 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Maciej (Matthew) Piechotka 2010-07-13 14:30:06 UTC
g-k-d starts consuming after some time of running 100% cpu. It does not respond to SIGTERM.

Stacktrace dane by attaching in middle of process (very strange lengths of line present).

Thread 13 (Thread 0x7f5f6937b710 (LWP 2790))

  • #0 do_sigwait
    from /lib/libpthread.so.0
  • #1 sigwait
    from /lib/libpthread.so.0
  • #2 signal_thread
    at gkd-main.c line 307
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

	Inferior 1 [process 2789] will be detached.

Quit anyway? (y or n) Detaching from program: /usr/bin/gnome-keyring-daemon, process 2789
Comment 1 Stef Walter 2010-09-11 18:50:09 UTC
Thanks for the detailed bug trace. I believe this commit fixes the problem:

commit d058611ba00db793450056caef1bb8079a2b5896
Author: Stef Walter <stef@memberwebs.com>
Date:   Sat Sep 11 18:45:44 2010 +0000

    [gpg-agent] Don't go into endless loop when client disconnects.
    
    If gpg-agent client disconnected without using QUIT, the daemon
    would go into an endless loop.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=624254