[Pidgin] #9402: IRC + SSL yield 100% CPU usage for a few minutes after connect

[Pidgin]

#9402: IRC + SSL yield 100% CPU usage for a few minutes after connect
------------------------------+---------------------------------------------
 Reporter:  Jinx              |     Owner:  elb  
     Type:  defect            |    Status:  new  
Component:  IRC               |   Version:  2.5.6
 Keywords:  IRC SSL 100% CPU  |  
------------------------------+---------------------------------------------
 When attempting to connect to irc.eversible.net or irc.rizon.net (Efnet
 and Rizon, respectively) via SSL, CPU usage goes to 100% for 1-5 minutes.
 The connection succeeds, and the behavior does not persist when
 reconnecting, but will exhibit itself again if Pidgin is restarted.

 The attached file is the debug window log set to the "warning" level. Two
 important lines are that of (19:01:16) followed by (19:03:30), which
 represents the time range during which CPU usage was 100%. I should note
 that, from another IRC client, I could see the Pidgin client login (and
 join the appropriate auto-join channels) at (19:01:16), so the issue seems
 to occur after the connection has been successfully established.

 This issue does not seem to exist with non-SSL servers (irc.efnet.net
 works fine). It also does not seem to be an issue with a particular SSL
 server: irc.zerofuzion.net. I am not certain of why this is.

 This issue has persisted since at least version 2.5.4, and I believe even
 earlier. I know this because, months ago, I attempted to troubleshoot this
 issue with a member of the Pidgin IRC channel on Freenode. After
 explaining the issue and testing a few scenarios, he encouraged me to file
 a bug report. I had hoped the issue would resolve itself in newer
 versions, but, since it hasn't, I've finally decided to submit this bug
 report.

 If anyone can reproduce this behavior and figure out the cause, I would
 greatly appreciate it. For reference, I am running Windows XP Home Edition
 with SP2, and my computer is not infected/littered with malware (according
 to AVG and Process Explorer). :) Thank you in advance.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9402>
Pidgin <http://pidgin.im>
Pidgin