[Pidgin] #7452: Failed to create pipe for communicating with child process (Too many open files)

[Pidgin]

#7452: Failed to create pipe for communicating with child process (Too many open
files)
---------------------+------------------------------------------------------
 Reporter:  Tythsai  |        Owner:           
     Type:  defect   |       Status:  new      
Milestone:           |    Component:  libpurple
  Version:  2.5.2    |   Resolution:           
 Keywords:           |  
---------------------+------------------------------------------------------
Description changed by Tythsai:

Old description:

> In Ubuntu Intrepid Ibex, Gnome desktop
> Pidgin 2.5.2
>
> When using pidgin for a long period of time, the program seems to spawn
> so many threads or subprocesses that trying to click hyperlinks in pidgin
> doesn't work and reports the error message above.
>
> My system is:
> Intel Core Duo
> 3 GB of ram
> 20 Gig's of free space
>
> currently my system is under fairly low load, with only 700 MB of ram in
> use.
>
> heres a sample of what "htop" spits out in the process view
> thats about a tenth of the total number of instances.
>
>  7752 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin
>  7817 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin
>  7838 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  7845 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  7850 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  7856 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  7922 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin
>  8031 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8036 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin
>  8375 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin
>  8443 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8781 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin
>  8926 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8932 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8942 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8950 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8959 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8969 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8980 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>  8986 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin
>

>

>

>

> heres the info from the debug window
> Unfortunately i couldn't get debug info from the program. I just ran it
> normally.
> Next time ill run it with the debugging output and ill post the results
> up here.
>

>

> (01:58:56) nautilus: Can't open the spool dir
> (01:58:56) util: Writing file prefs.xml to directory
> /home/jonesmz/.purple
> (01:58:56) util: Writing file /home/jonesmz/.purple/prefs.xml
> (01:58:56) util: Error opening file /home/jonesmz/.purple/prefs.xml.save
> for writing: Too many open files
> (01:58:59) nautilus: Can't open the spool dir
> (01:59:00) jabber: Sending (ssl): <iq type='get'
> id='purple1cb930aa'><ping xmlns='urn:xmpp:ping'/></iq>
> (01:59:00) jabber: Recv (ssl)(78): <iq
> to="eternalorb at gmail.com/Home4B4F4317" id="purple1cb930aa"
> type="result"/>
> (01:59:02) nautilus: Can't open the spool dir
> (01:59:05) nautilus: Can't open the spool dir
> (01:59:05) gtknotify: Executing xdg-open
> 'http://www.techeblog.com/index.php/tech-gadget/thiocyanide'
> (01:59:08) nautilus: Can't open the spool dir
>

> And apparently pidgin will eventually die without warning or error...
> which just happened a second ago.

New description:

 In Ubuntu Intrepid Ibex, Gnome desktop
 Pidgin 2.5.2

 When using pidgin for a long period of time, the program seems to spawn so
 many threads or subprocesses that trying to click hyperlinks in pidgin
 doesn't work and reports the error message above.

 My system is:
 Intel Core Duo
 3 GB of ram
 20 Gig's of free space

 currently my system is under fairly low load, with only 700 MB of ram in
 use.

 heres a sample of what "htop" spits out in the process view
 thats about a tenth of the total number of instances.

  7752 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin

  7817 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin

  7838 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  7845 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  7850 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  7856 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  7922 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin

  8031 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8036 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin

  8375 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin

  8443 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8781 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.02 pidgin

  8926 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8932 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8942 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8950 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8959 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8969 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8980 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin

  8986 jonesmz   20   0 3051M 75620 20768 S  0.0  2.4  0:00.00 pidgin









 heres the info from the debug window
 Unfortunately i couldn't get debug info from the program. I just ran it
 normally.
 Next time ill run it with the debugging output and ill post the results up
 here.




 (01:58:56) nautilus: Can't open the spool dir
 (01:58:56) util: Writing file prefs.xml to directory /home/jonesmz/.purple
 (01:58:56) util: Writing file /home/jonesmz/.purple/prefs.xml
 (01:58:56) util: Error opening file /home/jonesmz/.purple/prefs.xml.save
 for writing: Too many open files
 (01:58:59) nautilus: Can't open the spool dir
 (01:59:00) jabber: Sending (ssl): <iq type='get' id='purple1cb930aa'><ping
 xmlns='urn:xmpp:ping'/></iq>
 (01:59:00) jabber: Recv (ssl)(78): <iq
 to="eternalorb at gmail.com/Home4B4F4317" id="purple1cb930aa" type="result"/>
 (01:59:02) nautilus: Can't open the spool dir
 (01:59:05) nautilus: Can't open the spool dir
 (01:59:05) gtknotify: Executing xdg-open
 'http://www.techeblog.com/index.php/tech-gadget/thiocyanide'
 (01:59:08) nautilus: Can't open the spool dir


 And apparently pidgin will eventually die without warning or error...
 which just happened a second ago.

--

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7452#comment:1>
Pidgin <http://pidgin.im>
Pidgin