[issue43449] multiprocessing.Pool - crash in subprocess causes deadlock in parent
Jamie Kirkpatrick added the comment: More reading around this issue and I stumbled on an existing issue which this is a dup of so it can be closed. https://bugs.python.org/issue22393 -- stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.org/issue43449> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43449] multiprocessing.Pool - crash in subprocess causes deadlock in parent
New submission from Jamie Kirkpatrick : When using multiprocessing.Pool.apply[_async] a crash in the subprocess that is assigned the work item results in a deadlock in the parent process. The parent process remains blissfully unaware of the crash in the subprocess and waits for a result forever. The parent process treats this as normal since the thread running _maintain_pool handles dead processes and repopulates the pool with a replacement subprocess. See the test-case attached. Its not clear how this case should be handled but it can be very hard to trace issues in an application where this condition arises since all information about the crashing subprocess is lost (even with debug logging for the multiprocessing module enabled). -- components: Library (Lib) files: test.py messages: 388371 nosy: jkp priority: normal severity: normal status: open title: multiprocessing.Pool - crash in subprocess causes deadlock in parent type: behavior versions: Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 Added file: https://bugs.python.org/file49860/test.py ___ Python tracker <https://bugs.python.org/issue43449> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7140] imp.new_module does not function correctly if the module is returned from a function and used directly
New submission from Jamie Kirkpatrick j...@kirkconsulting.co.uk: See the testcase included. If you instead assign the result of the get_module() call to a variable and then make the call to the function defined in that module it works as expected. -- components: Library (Lib) files: testcase.py messages: 94082 nosy: jkp severity: normal status: open title: imp.new_module does not function correctly if the module is returned from a function and used directly type: behavior versions: Python 2.5, Python 2.6 Added file: http://bugs.python.org/file15133/testcase.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7140 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7140] imp.new_module does not function correctly if the module is returned from a function and used directly
Jamie Kirkpatrick j...@kirkconsulting.co.uk added the comment: Updated the testcase to show that the __dict__ for the module is incorrect unless the module is assigned to a temp variable. -- Added file: http://bugs.python.org/file15134/testcase.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7140 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
