Hi,
I believe I have found a method to reproduce this bug via ssh port
forwarding.
1) use SSH to create a port forward tunnel for jabber
eg: -L 5222:some.remote.host:5222
2) connect to the remote server via the tunnel (that is, set the jabber
prefs to connect to localhost:5222)
3) after the connection is up, exit the SSH connection and fully
terminate any forwarded ports via ctrl-c, if SSH does not exit on its own
Immediately thereafter, Pidgin will go into a 100% CPU usage loop, as
others in this bug have reported. If one restarts the SSH link
fairly quickly after, Pidgin will return to normal. However, if a long
period of time transpires with no connectivity, Pidgin appears to become
permanently non-responsive.
I suppose a dead remote machine might cause Pidgin to exhibit the same
behaviour?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
