[Pidgin] #15628: Pidgin leaks socket descriptors

Pidgin trac at pidgin.im
Tue May 7 01:26:52 EDT 2013


#15628: Pidgin leaks socket descriptors
--------------------+--------------------------
 Reporter:  anath   |      Owner:  rekkanoryo
     Type:  defect  |     Status:  new
Milestone:          |  Component:  unclassified
  Version:  2.10.7  |   Keywords:
--------------------+--------------------------
 i was running pidgin on Solaris. At some point of time, Pidgin will hung
 and I get the following messages :
 I get the following repeating messages :-

 xcb_connection_has_error() returned true
 shm_open() failed: Too many open files
 Failed to create secure directory: Too many open files
 socket(): Too many open files
 socket(): Too many open files


 (Pidgin:2193): GStreamer-CRITICAL **: file gstpoll.c: line 1544: assertion
 `set != NULL' failed

 (Pidgin:2193): GStreamer-CRITICAL **: file gstpoll.c: line 1544: assertion
 `set != NULL' failed

 (Pidgin:2193): GStreamer-CRITICAL **: file gstpoll.c: line 1544: assertion
 `set != NULL' failed

 (Pidgin:2193): GStreamer-CRITICAL **: file gstpoll.c: line 1544: assertion
 `set != NULL' failed

 (Pidgin:2193): GStreamer-CRITICAL **: file gstpoll.c: line 1544: assertion
 `set != NULL' failed


 I looked into it and looks like Pidgin is leaking file descriptors while
 using IRC protocol. It looks like, if I ping someone in IRC channel and if
 the person is in IDLE state, Pidgin is leaking file descriptors (Socket).

 [tank:~]$ pfiles `pgrep pidgin` | grep mode | wc -l
      251

 Seem we have a load of AF_UNIX sockets being created. Not really sure what
 they are for and I have noticed a creeping increase of them over time.

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


More information about the Tracker mailing list