[issue6147] multithreading.Pool.map() crashes Windows computer

Merlijn van Deen added the comment: Two questions: (1) can this be at least be added as a big fat warning in the documentation? (2) would it be a reasonable option to let either (a) the creation of a Pool (b) executing something using the Pool cause an exception when it happens during the im

[issue6147] multithreading.Pool.map() crashes Windows computer

Changes by Benjamin Peterson : -- status: -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6147] multithreading.Pool.map() crashes Windows computer

Jesse Noller added the comment: Hey Alex; This isn't a bug, or a feature request. On win32, the way multiprocessing fakes a fork() is by creating a special subprocess which essentially imports and executes the function/process to be run, communication is handled through pickling and pipes. F

[issue6147] multithreading.Pool.map() crashes Windows computer

Alex James added the comment: Ok Jesse, that did stop the bomb problem. Unfortunately the real code belongs in a scientific research distributable module that is called by another function in the module where both have been imported into the script that is run. So it isn't being called by __m

[issue6147] multithreading.Pool.map() crashes Windows computer

Jesse Noller added the comment: Can you wrap the execution of the main code in a if __name__ == "__main__": block, as shown in the documentation? Failure to do so can cause a fork bomb on windows -- ___ Python tracker

[issue6147] multithreading.Pool.map() crashes Windows computer

Changes by Benjamin Peterson : -- assignee: -> jnoller nosy: +jnoller status: open -> ___ Python tracker ___ ___ Python-bugs-list mai

[issue6147] multithreading.Pool.map() crashes Windows computer

New submission from Alex James : When calling multithreading.Pool().map() to distribute computational load I've recently got system crashes. The attached minimalist script exhibits this issue. On a Windows Vista home premium sp1 running Python 2.6.2 on a dual-core laptop, the script stops ex