[Pidgin] #11531: Pidgin crashes with "Error creating reader thread: Not enough space"

Pidgin trac at pidgin.im
Tue Mar 9 18:15:56 EST 2010


#11531: Pidgin crashes with "Error creating reader thread: Not enough space"
-------------------------------------+--------------------------------------
 Reporter:  jmlsteele                |     Owner:  datallah
     Type:  defect                   |    Status:  new     
Component:  winpidgin (gtk)          |   Version:  2.6.6   
 Keywords:  gio reader thread win32  |  
-------------------------------------+--------------------------------------
 A few times in the past pidgin has become unresponsive sometime during the
 day while I'm at school, and I don't notice it until I get home.  I
 finally decided to try and find the problem, so i installed the debug
 version (win32) and had it save the debug log.  When i came home today
 (roughly 18:00) I noticed that it had crashed again (although crash isn't
 right, as by all indications pidgin is still running, it just doesn't
 respond).

 The last line in my debug log (which is over 1mb, so I'll upload it on
 request, but it's mostly irrelevant) was the following..
 {{{
 (14:22:17) g_log: win32/giowin32.c:210: Error creating reader thread: Not
 enough space
 }}}
 To put this in some context, here are the 20 previous lines (replace my
 gmail address with a placeholder)
 {{{
 (14:16:48) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe132c" type="result"/>
 (14:17:18) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe132d'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:17:18) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe132d" type="result"/>
 (14:17:48) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe132e'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:17:48) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe132e" type="result"/>
 (14:18:18) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe132f'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:18:18) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe132f" type="result"/>
 (14:18:48) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe1330'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:18:48) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe1330" type="result"/>
 (14:19:18) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe1331'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:19:18) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe1331" type="result"/>
 (14:19:32) jabber: Recv (ssl)(1):
 (14:20:18) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe1332'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:20:18) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe1332" type="result"/>
 (14:20:48) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe1333'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:20:48) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe1333" type="result"/>
 (14:21:18) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe1334'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:21:18) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe1334" type="result"/>
 (14:21:48) jabber: Sending (ssl) (%GMAILADDRESS%/HomeF0CC3CB6): <iq
 type='get' id='purple3bfe1335'><ping xmlns='urn:xmpp:ping'/></iq>
 (14:21:48) jabber: Recv (ssl)(77): <iq to="%GMAILADDRESS%/HomeF0CC3CB6"
 id="purple3bfe1335" type="result"/>
 }}}

 Based on the time stamps it looks like it was about to send another ping
 message, but couldn't for some reason.

 If requested I can post/send/upload more of the log, but I'd have to edit
 out some of it as I noticed my friends were listed in it.

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


More information about the Tracker mailing list