[Pidgin] #9382: Thread leak: some created threads are never destroyed

[Pidgin]

#9382: Thread leak: some created threads are never destroyed
--------------------------+-------------------------------------------------
 Reporter:  speed47       |     Owner:  rekkanoryo
     Type:  defect        |    Status:  new       
Component:  unclassified  |   Version:  2.5.6     
 Keywords:  threads leak  |  
--------------------------+-------------------------------------------------
 The number of threads attached to Pidgin never stops increasing,
 eventually leading to kernel process' space exhaustion, leading to severe
 system instability (all fork()s are denied system-wide).

 I'm running Pidgin 2.5.6 under Fedora 11, all plugins have been disabled,
 and I'm connected to one MSN Messenger and one Jabber/XMPP account. I've
 left Pidgin mainly idle sitting in the taskbar.

 Attached is a Pidgin session I ran under gdb during 4 hours, with debug
 symbols installed. One can see each thread creation (and the fewer threads
 destructions). I then used CTRL+C to type some commands that may be of
 some use to find the cause : info threads, bt full, bt. I also switched to
 random threads and ran "bt" under their context, where we can see that
 each thread is stuck at the same place in the code.

 At the end of the attachment, is the output of a "ps" command, where we
 can see the creation date of each thread.

 If any further info is needed, I can reproduce this easily : I just have
 to launch Pidgin, and wait ! So don't hesitate to ask :)

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