SRU Request: telepathy logger uses 100% CPU

I confirm this one, which should be fixed by http://cgit.freedesktop.org/telepathy/telepathy-logger/commit/?id=884c52dad5d5fb30a450b013b83aed306ed49164

I'm having a look at uploading it to debian

This bug was fixed in the package telepathy-logger - 0.2.6-1ubuntu1

---------------
telepathy-logger (0.2.6-1ubuntu1) natty; urgency=low

  * debian/patches/git_eat_cpu.patch: git commit to fix a case where
    telepathy-logger can start eating cpu (lp: #745803)
 -- Sebastien Bacher <email address hidden> Thu, 31 Mar 2011 15:52:35 +0200

Bug appeared again today for me. Unfortunately, killing telepathy-logger doesn't work anymore as a new instance immediately spawn.

Bug is appearing for me at this instant. Was having a conversation a minute ago and even closing empathy didn't help. `killall telepathy logger` worked when empathy wasn't running.

telepathy-logger:
  Installiert: 0.2.6-1ubuntu1
  Kandidat: 0.2.6-1ubuntu1
  Versionstabelle:
 *** 0.2.6-1ubuntu1 0
       1002 http://archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

Same problem, fully updated (0.2.6-1ubuntu1) just like jinns.

Exact same situation, killall works when empathy is not running, else it respawns and starts to use all my CPU. I noticed it because I was having problem rendering HD videos, so it is an issue for me :)

Other than this, I've been very happy with newer versions of empathy (and I used to kinda hate it at first). Keep up the great work :)

Another temporary workaround is to uncheck "Log conversations" checkbox in empathy properties.

Same problem (100% cpu usage) usingtelepathy-logger 0.2.6-1ubuntu1 on Ubuntu 11.04.

 I already "Log conversations" unchecked, so that didn't resolved the issue for me.

I've attached sysprof generated log of the system. I attached gdb to the running process, and interrupted a couple times (aka poor man's profiler), somewhere inside _tpl_action_chain_continue seems to be common hotspot.

#0 0xb75eb436 in g_atomic_pointer_get () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1 0xb738beb5 in tp_message_get_type () from /usr/lib/libtelepathy-glib.so.0
#2 0xb788285f in ?? () from /usr/lib/libtelepathy-logger.so.2
#3 0xb7870be3 in _tpl_action_chain_continue () from /usr/lib/libtelepathy-logger.so.2
#4 0xb7882ae2 in ?? () from /usr/lib/libtelepathy-logger.so.2
#5 0xb7354093 in ?? () from /usr/lib/libtelepathy-glib.so.0
#6 0xb7356eed in ?? () from /usr/lib/libtelepathy-glib.so.0
#7 0xb732c48b in ?? () from /usr/lib/libtelepathy-glib.so.0
#8 0xb739e70a in ?? () from /usr/lib/libtelepathy-glib.so.0
#9 0xb7612311 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb7616aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb7617270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#12 0xb761792b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#13 0x0804945e in ?? ()
#14 0xb715be37 in __libc_start_main (main=0x8049180, argc=1, ubp_av=0xbfbe1ea4, init=0x80494f0, fini=0x8049550, rtld_fini=0xb78b3a50,
    stack_end=0xbfbe1e9c) at libc-start.c:226
#15 0x08048f71 in ?? ()

#0 0xb76ee976 in g_type_check_instance_is_a () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#1 0xb738d385 in tp_message_get_sent_timestamp () from /usr/lib/libtelepathy-glib.so.0
#2 0xb7881571 in ?? () from /usr/lib/libtelepathy-logger.so.2
#3 0xb7882873 in ?? () from /usr/lib/libtelepathy-logger.so.2
#4 0xb7870be3 in _tpl_action_chain_continue () from /usr/lib/libtelepathy-logger.so.2
#5 0xb7882ae2 in ?? () from /usr/lib/libtelepathy-logger.so.2
#6 0xb7354093 in ?? () from /usr/lib/libtelepathy-glib.so.0
#7 0xb7356eed in ?? () from /usr/lib/libtelepathy-glib.so.0
#8 0xb732c48b in ?? () from /usr/lib/libtelepathy-glib.so.0
#9 0xb739e70a in ?? () from /usr/lib/libtelepathy-glib.so.0
#10 0xb7612311 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb7616aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#12 0xb7617270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#13 0xb761792b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#14 0x0804945e in ?? ()
#15 0xb715be37 in __libc_start_main (main=0x8049180, argc=1, ubp_av=0xbfbe1ea4, init=0x80494f0, fini=0x8049550, rtld_fini=0xb78b3a50,
    stack_end=0xbfbe1e9c) at libc-start.c:226
#16 0x08048f71 in ?? ()
0xb76055af in g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0

#0 0xb76055af in g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1 0xb7367518 in tp_asv_get_uint32 () from /usr/lib/libtelepathy-glib.so.0
#2 0xb7881344 in ?? () from /usr/lib/libtelepathy-logger.so.2
#3 0xb7882857 in ?? () from /usr/lib/libtelepathy-logger.so.2
#4 0xb7870be3 in _tpl_action_chain_continue () from /usr/lib...

I'm seeing this also, huge spikes for CPU use in Natty. 50+% in a dual core system.

You probably want more debugging symbols for that backtrace as the problem is more likely to be within telepathy.

Why does this say fix released when there is still a problem? I'm running Natty. Thanks in advance

Seems this is still an issue for certain people, so I have reopened. There's a comment in the section of code at http://cgit.freedesktop.org/telepathy/telepathy-logger/tree/telepathy-logger/text-channel.c?id=884c52dad5d5fb30a450b013b83aed306ed49164#n629 where they mention that the channel ID doesn't work anymore, and this may be where the hangup is again.

Also, those who have this issue, if you can cause it to happen, please let us know the steps you took to do so.

happens often when I recover from sleep/hibernate. disabling "log conversations" does not help

Doing a suspend-resume cycle triggers this bug for me, but not _all_ the time. I'm not sure what exactly the conditions for it are.

Looks like the patch is not applied in 0.2.6-1ubuntu1.

The patch is in debian/patches directory but a series file is missing

I'll try to get this patch fixed in natty.

same problen here in ubuntu11.04

Looks like the patch is not applied in 0.2.6-1ubuntu1.

The patch is in debian/patches directory but a series file is missing

Same problem here in ubuntu 11.04

Uploaded to -proposed, awaiting SRU processing.

Accepted telepathy-logger into natty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

thanks so much for working on it. was really a pain in the neck.

looks much better now. will check again after some days uptime + hibernate cycles

The natty-proposed package worked for me.

I was observing the 100% telepathy-logger CPU usage consistently every morning after upgrading to natty. I installed the natty-proposed package (Thanks for the EnableProposed link, btw) two days ago, and I haven't observed the problem since.

Thanks to Günter and Ben for testing. Marking as verification-done

This bug was fixed in the package telepathy-logger - 0.2.6-1ubuntu1.2

---------------
telepathy-logger (0.2.6-1ubuntu1.2) natty-proposed; urgency=low

  * debian/patches/series
    -Add series file (LP: #745803)
  * debian/patches/git_eat_cpu.patch
    -Updated typo in patch
 -- Brian Curtis <email address hidden> Fri, 13 May 2011 15:57:42 -0400

This problem is not fixed and it's forcing me to use other chat clients because it burns up my battery life. I just saw telepathy-logger hogging 60% of my CPU. I'll give any information that you need as this problem is a serious concern. Thank you