[Bug 60765] Re: Gnome-keyring-daemon takes up 100% CPU and all memory
Yachar
yach at free.fr
Mon Sep 18 18:26:04 UTC 2006
Thanks for your answer.
My gconf issues were I had no writable paths. I solved it with a ~/.gconf.paths (see bug #60443).
Maybe I messed up my config, but I don't play with those config files unless I'm forced to ;)
I don't think that's an issue with my computer as it did work very well
with Dapper. But something might have gone wrong since then.
I launched gnome-keyring-manager, then
gdb -p $(pidof gnome-keyring-daemon)
and the trace is below. Hope this helps (though it doesn't look very useful).
I have two gnome-keyring-daemon entries in the process list (ps uax) :
one that is stable (0.0 CPU and 10 Mo RAM), and the other constantly
growing. It might be a fork or a thread.
(gdb) thread apply all bt
Thread 1 (Thread 47489959526176 (LWP 4617)):
#0 0x00002b311e017527 in access () from /lib/libc.so.6
#1 0x00002b311dcc1f3d in g_file_test () from /usr/lib/libglib-2.0.so.0
#2 0x000000000040b389 in ?? ()
#3 0x0000000000000000 in ?? ()
#0 0x00002b311e017527 in access () from /lib/libc.so.6
(gdb)
--
Gnome-keyring-daemon takes up 100% CPU and all memory
https://launchpad.net/bugs/60765
More information about the desktop-bugs
mailing list