[Bug 27801] New: Logger causes dbus-deamon to use 100% cpu when starting chat

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=27801

           Summary: Logger causes dbus-deamon to use 100% cpu when
                    starting chat
           Product: Telepathy
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: logger
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: qsorix at gmail.com
         QAContact: telepathy-bugs at lists.freedesktop.org


When I open new chat window in empathy, dbus-deamon starts to utilize 100% of
CPU for about a minute and the chat window opens with 15 seconds delay.

Steps to reproduce:
1. (optional) Start dbus-deamon in debug mode and export new 
DBUS_SESSION_BUS_ADDRES.
2. Start empathy.
3. At this point telepathy-gabble, telepathy-logger and mission-control-5 are
running.
4. Open roster, double click on any contact.

Result:
CPU utilization by dbus-deamon goes to 100%, chat window opens but after about
15 seconds delay. After some time CPU goes down to normal. During this period
dbus works (i.e. all communication proceeds without interruptions)

Expected result:
Chat window opens instantly. Dbus-deamon is not affected

I've noticed that if I kill telepathy-logger and let it start by itself (I
don't know how it is started), then this bug still happens but this time
without cpu burning -- just the delay before opening chat window. If i kill
telepathy-logger again and run it myself from terminal, it is the same again
(delay and 100% cpu).

If I kill telepathy-logger and prevent it from starting (e.g. mv binary)
everything works as expected. I don't have to restart dbus or empathy or
anything.

dbus-monitor shows no intensive communication during that period.

I tried to get some logs from telepathy-logger or dbus but failed. dbus running
in debug mode doesn't output anything at the time I double click a contact. I
don't know how to make telepathy-logger print some debug info. I've emerged it
with USE=debug but it still doesn't print a thing.

I've run it like this: LOGGER_PERSIST=1 LOGGER_DEBUG=all
/usr/bin/telepathy-logger

Give me some tips, please, I'll attach logs then.

I'm using:

telepathy-gabble 0.8.8
telepathy-logger 0.1.1
telepathy-mission-control 5.2.5
telepathy-salut 0.3.10
empathy 2.30.0.1

dbus 1.2.24
dbus-glib 0.86
telepathy-glib 0.10.1
glib 2.24.0

kernel 2.6.31-gentoo-r6 

gcc (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2

Everything was emerged from gentoo's ebuilds using
CFLAGS="-march=k8-sse3 -mmmx -m3dnow -O2 -pipe"

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.