I just realized that Gabble is using 100% of my CPU. Here is the backtrace if I interrupt it: (sorry for the lack of debugging symbols!) #0 0x00007f51e5ad4bc5 in __libc_send (fd=9, buf=0x1a68520, n=4408, flags=0) at ../sysdeps/unix/sysv/linux/x86_64/send.c:28 #1 0x00007f51e50a4c8a in _gnutls_io_write_buffered () from /usr/lib/libgnutls.so.26 #2 0x00007f51e50a4f29 in _gnutls_io_write_flush () from /usr/lib/libgnutls.so.26 #3 0x00007f51e50a108b in _gnutls_send_int () from /usr/lib/libgnutls.so.26 #4 0x00007f51e6fd9f20 in ?? () from /usr/lib/libloudmouth-1.so.0 #5 0x00007f51e6fdc891 in ?? () from /usr/lib/libloudmouth-1.so.0 #6 0x00007f51e6fd48d6 in ?? () from /usr/lib/libloudmouth-1.so.0 #7 0x00007f51e6fd4e98 in lm_connection_send () from /usr/lib/libloudmouth-1.so.0 #8 0x0000000000412f83 in ?? () #9 0x00000000004322a3 in ?? () #10 0x0000000000432358 in ?? () #11 0x0000000000432548 in ?? () #12 0x00007f51e6fd6d39 in ?? () from /usr/lib/libloudmouth-1.so.0 #13 0x00007f51e6fd8207 in ?? () from /usr/lib/libloudmouth-1.so.0 #14 0x00007f51e5f1ff7a in IA__g_main_context_dispatch (context=0x14cebb0) at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:1814 #15 0x00007f51e5f23640 in g_main_context_iterate (context=0x14cebb0, block=1, dispatch=1, self=<value optimized out>) at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2448 #16 0x00007f51e5f23b0d in IA__g_main_loop_run (loop=0x14cb670) at /tmp/cdt.XX50MgKl/build-area/glib2.0-2.20.1/glib/gmain.c:2656 #17 0x00007f51e6b54a48 in tp_run_connection_manager () from /usr/lib/libtelepathy-glib.so.0 #18 0x00007f51e57925a6 in __libc_start_main (main=0x4120c0 <tp_svc_channel_type_tubes_implement_offer_stream_tube@plt+264>, argc=1, ubp_av=0x7fffefe888e8, init=0x47e910, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffefe888d8) at libc-start.c:222 #19 0x0000000000411ff9 in ?? () #20 0x00007fffefe888d8 in ?? () #21 0x000000000000001c in ?? () #22 0x0000000000000001 in ?? () #23 0x00007fffefe88c5a in ?? () #24 0x0000000000000000 in ?? ()
This is a Loudmouth bug. Will has some patches to fix it, but hasn't pushed them upstream yet.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.