Issue 15646: multiprocessing can do equivalent of a fork bomb on Windows (original) (raw)

Issue15646

Created on 2012-08-14 10:34 by sbt, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg168189 - (view)	Author: Richard Oudkerk (sbt) *	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