[Pidgin] #12256: Pidgin not responding with "Error creating reader thread: Not enough space"

[Pidgin]

#12256: Pidgin not responding with "Error creating reader thread: Not enough space"
--------------------------+-------------------------------------------------
 Reporter:  jeffd         |     Owner:  rekkanoryo
     Type:  defect        |    Status:  new       
Component:  unclassified  |   Version:  2.7.1     
 Keywords:  threads       |  
--------------------------+-------------------------------------------------
 For the past week, any time pidgin is running and connected for a few
 hours, it stops responding (the window won't redraw, has an hour glass and
 windows labels it as "Not Responding). If I try to close the window,
 windows let's me kill the process. The debug log shows:



 {{{

 (23:45:16) g_log: win32/giowin32.c:238: Error binding to reset_send
 socket: An operation on a socket could not be performed because the system
 lacked sufficient buffer space or because a queue was full.

 (23:45:16) g_log: win32/giowin32.c:255: Error binding to reset_recv
 socket: An operation on a socket could not be performed because the system
 lacked sufficient buffer space or because a queue was full.

 (23:45:16) g_log: win32/giowin32.c:262: Error getsockname with reset_recv
 socket: An invalid argument was supplied.

 (23:45:16) g_log: win32/giowin32.c:273: connect to reset_recv socket: An
 operation on a socket could not be performed because the system lacked
 sufficient buffer space or because a queue was full.

 (23:45:16) g_log: win32/giowin32.c:238: Error binding to reset_send
 socket: An operation on a socket could not be performed because the system
 lacked sufficient buffer space or because a queue was full.

 (23:45:16) g_log: win32/giowin32.c:255: Error binding to reset_recv
 socket: An operation on a socket could not be performed because the system
 lacked sufficient buffer space or because a queue was full.

 (23:45:16) g_log: win32/giowin32.c:262: Error getsockname with reset_recv
 socket: An invalid argument was supplied.

 (23:45:16) g_log: win32/giowin32.c:273: connect to reset_recv socket: An
 operation on a socket could not be performed because the system lacked
 sufficient buffer space or because a queue was full.

 (23:45:16) g_log: win32/giowin32.c:210: Error creating reader thread: Not
 enough space

 }}}


 When this happens, the Windows Task Manager shows about 1800 total
 threads. After I kill pidgin, the thread count goes down to around 900. So
 somehow pidgin is creating lots and lots of threads and then freezing due
 to resource exhaustion. The effect is very similar to Ticket #11531,
 except that pidgin seems to be the source of the thread use.

 This is repeatable every time I leave pidgin running. Is there any more
 useful information I can provide?

 Thanks!

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