classification
Title: multiprocessing can do equivalent of a fork bomb on Windows
Type: behavior Stage: resolved
Components: Versions: Python 3.2, Python 3.3, Python 2.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: python-dev, sbt
Priority: normal Keywords:

Created on 2012-08-14 10:34 by sbt, last changed 2012-08-14 15:35 by sbt. This issue is now closed.

Messages (2)
msg168189 - (view) Author: Richard Oudkerk (sbt) * (Python committer) Date: 2012-08-14 10:34
If the "if __name__ == '__main__'" idiom is not used on Windows you can get the recursive starting of new processes.

This is because importing the main module in a child process starts a new child process as a side effect.

There is a test intended to prevent this and raise RuntimeError instead, but it is currently ineffective.
msg168193 - (view) Author: Roundup Robot (python-dev) Date: 2012-08-14 11:55
New changeset e4fe1daef9f7 by Richard Oudkerk in branch '2.7':
Issue #15646: Prevent equivalent of a fork bomb when using multiprocessing
http://hg.python.org/cpython/rev/e4fe1daef9f7

New changeset 20f8a2455ffb by Richard Oudkerk in branch '3.2':
Issue #15646: Prevent equivalent of a fork bomb when using multiprocessing
http://hg.python.org/cpython/rev/20f8a2455ffb
History
Date User Action Args
2012-10-16 14:11:04sbtlinkissue16246 superseder
2012-08-14 15:35:52sbtsetstatus: open -> closed
resolution: fixed
stage: resolved
2012-08-14 11:55:21python-devsetnosy: + python-dev
messages: + msg168193
2012-08-14 10:34:32sbtcreate