This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients lukasz.langa, nadeem.vawda, vstinner
Date 2011-01-07.09:13:12
SpamBayes Score 2.8964335e-09
Marked as misclassified No
Message-id <1294391704.14078.0.camel@marge>
In-reply-to <1294366779.15.0.0946107332291.issue10512@psf.upfronthosting.co.za>
Content
Le vendredi 07 janvier 2011 à 02:19 +0000, Nadeem Vawda a écrit :
> Most of these leaks seem to stem from the fact that socket.SocketIO.close() doesn't behave as documented. According to its docstring, it is meant to decrement the underlying socket's refcount, and close it if the refcount drops to zero. However, to do this job it calls socket._decref_socketios(), which is defined as follows:
> 
>     def _decref_socketios(self):
>         if self._io_refs > 0:
>             self._io_refs -= 1
>         if self._closed:
>             self.close()
> 
> Clearly, this doesn't do what the docstring describes. Changing the second conditional from "if self._closed:" to "if self._io_refs <= 0:" disposes of all but one of the ResourceWarnings, but also breaks 8 tests in test_socket. It seems that the tests expect a socket to remain open after all referring SocketIO objects have been closed, which contradicts the docstring for SocketIO.close(). I suppose I should open a separate issue for this.

Can you please open a new issue for that?

Victor
History
Date User Action Args
2011-01-07 09:13:14vstinnersetrecipients: + vstinner, nadeem.vawda, lukasz.langa
2011-01-07 09:13:12vstinnerlinkissue10512 messages
2011-01-07 09:13:12vstinnercreate