Package: mcabber
Version: 0.9.7-0.1
Severity: normal
After the message "[Jabber] Not connected to the server", while waiting for the
next reconnect attempt, mcabber consumes 100% CPU.
This happens both when mcabber is started and not able to connect at all, and
whan mcabber was connected, but then lost the connection for whatever reason.
As soon as the "waiting" state is over (it either managed to reconnect to the
server, or the user typed /disconnect), mcabber stops eating up cputime as well.
Also, if mcabber notices the server is not reachable at all ("Unable to connect
to the server"), it does not consume 100% CPU.
I could reproduce this on two Debian machines (testing and unstable).
I assume the problem is related to the code piece responsible for waiting for
the next reconnect attempt.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mcabber depends on:
ii libaspell15 0.60.6-1 GNU Aspell spell-checker runtime l
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libglib2.0-0 2.16.6-1 The GLib library of C routines
ii libgpg-error0 1.4-2 library for common error values an
ii libgpgme11 1.1.6-2 GPGME - GnuPG Made Easy
ii libncursesw5 5.7+20081213-1 shared libraries for terminal hand
ii libotr2 3.2.0-1 Off-the-Record Messaging library
ii libssl0.9.8 0.9.8g-14 SSL shared libraries
mcabber recommends no packages.
mcabber suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
