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.

classification
Title: Cleanup up ResourceWarnings in multiprocessing
Type: resource usage Stage: needs patch
Components: Library (Lib) Versions: Python 3.4, Python 3.5, Python 2.7
process
Status: closed Resolution: out of date
Dependencies: Superseder: test_multiprocessing_spawn ResourceWarning with -Werror
View: 25654
Assigned To: Nosy List: BreamoreBoy, asksol, jnoller, sbt, vstinner
Priority: normal Keywords:

Created on 2010-11-04 01:03 by brian.curtin, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg120367 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-11-04 01:03
As shown in a debug run of test_multiprocessing, at least two places in managers.py apparently leave open sockets. Lines 786 and 805 are the culprits, both util log lines.
msg120382 - (view) Author: Ask Solem (asksol) (Python committer) Date: 2010-11-04 08:28
ah, this is something I've seen as well, its part of a bug that I haven't created an issue for yet.
msg223296 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-07-16 23:22
I've looked at managers.py and can't see any evidence that the sockets are ever closed.  Please check this out as I can't believe that a technical problem like this could have been around for so long without someone else spotting it during testing, thus meaning that my eyesight is deficient.
msg262355 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-03-24 15:12
Sorry but without any information about the module or function which emits such ResourceWarning, I prefer to close the issue.

Anyway, with Python 3.6, it became trivial to identify the root cause of ResourceWarning warinings:
https://docs.python.org/dev/whatsnew/3.6.html#warnings

So it should now be much easier to fix them.
msg262357 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2016-03-24 15:23
Oh, I found the issue #25654 which contains more information and even patches.
History
Date User Action Args
2022-04-11 14:57:08adminsetgithub: 54514
2016-03-24 15:23:35vstinnersetsuperseder: test_multiprocessing_spawn ResourceWarning with -Werror
messages: + msg262357
2016-03-24 15:12:36vstinnersetstatus: open -> closed

nosy: + vstinner
messages: + msg262355

resolution: out of date
2014-07-17 13:57:58brian.curtinsetnosy: - brian.curtin
2014-07-16 23:22:38BreamoreBoysetnosy: + BreamoreBoy, jnoller, sbt

messages: + msg223296
versions: + Python 2.7, Python 3.4, Python 3.5, - Python 3.2
2010-11-04 08:28:56asksolsetmessages: + msg120382
2010-11-04 01:03:32brian.curtincreate