I have no idea what's going on, the tube works perfectly even if gabble is taking 100% CPU. After closing the tube, gabble still takes 100% CPU.
See attached logs.
Note: I attached gabble into gdb and interupted it, but it's always in mainloop's poll function. So probably an idle callback that keep running?
Created attachment 40869 [details]
Looks like this happens only when channel request fails
I confirm the same situation.
$ lsb_release -rd
Description: Ubuntu 10.10
$ apt-cache policy telepathy-gabble
*** 0.10.0-1 0
500 http://br.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
Everytime I attempt to connect on Gtalk, I get a connection error and this process - telepathy_gabble - consumes > 100% of my CPU.
Problem is only solved when all networks connect or when empathy is closed.
If you need more information, just ask.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/116.