[issue16246] Multiprocessing infinite loop on Windows

Changes by Richard Oudkerk : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue16246] Multiprocessing infinite loop on Windows

Richard Oudkerk added the comment: I think this is a duplicate of Issue #15646 which has been fixed in the 2.7 and 3.x branches. If you run Lib/test/mp_fork_bomb.py you should get a RuntimeError with a helpful message telling you to use the 'if __name__ == "__main__"' idiom. -- resolu

[issue16246] Multiprocessing infinite loop on Windows

Tim Golden added the comment: The natural way to do this in windows is using the Job API: http://msdn.microsoft.com/en-us/library/windows/desktop/ms684161%28v=vs.85%29.aspx However I'm not sure where to apply this within the multiprocessing architecture (or if it's even a good idea). -

[issue16246] Multiprocessing infinite loop on Windows

Changes by R. David Murray : -- nosy: +sbt type: -> behavior versions: +Python 3.4 -Python 3.1 ___ Python tracker ___ ___ Python-bugs

[issue16246] Multiprocessing infinite loop on Windows

New submission from Ethan Furman: On Windows multiprocessing has a well known limitation: because there is no fork() new shells must be invoked, and if the call that ultimately starts multiprocessing is not guarded by an `if __name__ == '__main___'` check an infinite loops results and you have