Public bug reported:
trackerd frequently eats CPU after opening a desktop session. I've just
debugged this once, but it appears to be stuck at the following:
(gdb) where
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7c539f6 in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7cee962 in g_usleep () from /usr/lib/libglib-2.0.so.0
#3 0x0804e9ec in do_cleanup (sig_msg=0x8093249 "DBus connection lost")
at trackerd.c:239
#4 0x0805039a in local_dbus_connection_monitoring_message_func (
connection=0x80f3058, message=0x80f3688, data=0x0) at trackerd.c:1890
#5 0xb7ea462b in ?? () from /usr/lib/libdbus-1.so.3
#6 0x080f3058 in ?? ()
#7 0x080f3688 in ?? ()
#8 0x00000000 in ?? ()
I don't know much about DBus, but it appears to be running:
$ ps -ef | grep dbus
darrenw 2460 1860 0 23:06 pts/1 00:00:00 grep dbus
103 7122 1 0 16:53 ? 00:00:00 /usr/bin/dbus-daemon --system
root 7178 7177 0 16:53 ? 00:00:00 dbus-daemon --session
--print-address --nofork
darrenw 16323 1 0 18:12 ? 00:00:00 dbus-daemon --fork
--print-address 29 --print-pid 31 --session
darrenw 16377 1 0 18:12 ? 00:00:00 /usr/bin/dbus-daemon --fork
--print-pid 11 --print-address 13 --session
darrenw 16378 1 0 18:12 ? 00:00:00 dbus-launch --autolaunch
bc8d5bc16e612742c86e050045ccf000 --binary-syntax --close-stderr
** Affects: tracker (Ubuntu)
Importance: Undecided
Status: New
--
Eats CPU after DBus connection lost
https://bugs.launchpad.net/bugs/162579
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
