[issue33966] test_multiprocessing_spawn.WithProcessesTestPool.test_traceback() leaks 4 handles on Windows

STINNER Victor added the comment: I give up on that one :-( It doesn't seem easy to fix this corner case without changing the behaviour. -- resolution: -> out of date stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue33966] test_multiprocessing_spawn.WithProcessesTestPool.test_traceback() leaks 4 handles on Windows

Change by STINNER Victor : -- pull_requests: +7573 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33966] test_multiprocessing_spawn.WithProcessesTestPool.test_traceback() leaks 4 handles on Windows

Change by STINNER Victor : -- keywords: +patch pull_requests: +7572 stage: -> patch review ___ Python tracker ___ ___

[issue33966] test_multiprocessing_spawn.WithProcessesTestPool.test_traceback() leaks 4 handles on Windows

STINNER Victor added the comment: > * dump() indirectly calls reduce_connection() (ex: for SimpleQueue._reader) > of multiprocessing.connection > * reduce_connection() duplicates the pipe handle Sorry, it's reduce_pipe_connection(), not reduce_connection(). > It's unclear to me who is

[issue33966] test_multiprocessing_spawn.WithProcessesTestPool.test_traceback() leaks 4 handles on Windows

STINNER Victor added the comment: * Pool._repopulate_pool() creates processes with args=(self._inqueue, ...) * Pool._inqueue is a multiprocessing.queues.SimpleQueue * Process.__init__() of multiprocessing.popen_spawn_win32 calls reduction.dump(process_obj, to_child) which indirectly contains

[issue33966] test_multiprocessing_spawn.WithProcessesTestPool.test_traceback() leaks 4 handles on Windows

New submission from STINNER Victor : Using my PR 7827, the following command shows a leak of 4 Windows handles per run: python -m test -R 3:3 test_multiprocessing_spawn -v -m test.test_multiprocessing_spawn.WithProcessesTestPool.test_traceback See also bpo-33929: test_multiprocessing_spawn: