[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Antoine Pitrou : -- resolution: -> rejected stage: -> resolved status: pending -> closed ___ Python tracker ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Antoine Pitrou added the comment: Roman, do you think my analysis above is wrong? Otherwise, I'm inclined to close the issue. -- status: open -> pending ___ Python tracker

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Antoine Pitrou added the comment: As for Process, it doesn't have a close() method right now, so you should lose all references to a Process object once you are done with it. When a Process is garbage-collected, its Popen object is garbage-collected too, and the Popen object's Finalizer then

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Antoine Pitrou added the comment: As for Queue._writer, I don't think this is true. When you call Queue.close(), it calls the _close() method, which sends a sentinel to the feeder thread (see _finalize_close), and the feeder thread then pops the sentinel, closes the writer and exits.

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Antoine Pitrou added the comment: The Process issue will be fixed with Process.close() in issue30596. -- nosy: +pitrou ___ Python tracker ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Josh Rosenberg : -- nosy: +josh.r ___ Python tracker ___ ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Raymond Hettinger : -- assignee: -> davin ___ Python tracker ___ ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Camilla Montonen : -- nosy: +Winterflower ___ Python tracker ___ ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Roman Bolshakov : Removed file: http://bugs.python.org/file43046/leak.py ___ Python tracker ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Roman Bolshakov added the comment: multiprocessing.Queue._writer is affected by similar issue. _writer FD is left open after .close() is invoked on a Queue. -- Added file: http://bugs.python.org/file43642/leak.py ___ Python tracker

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by Марк Коренберг : -- nosy: +mmarkk ___ Python tracker ___ ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

Changes by SilentGhost : -- nosy: +jnoller, sbt versions: +Python 3.6 -Python 3.3, Python 3.4 ___ Python tracker ___

[issue27151] multiprocessing.Process leaves read pipes open (Process.sentinel)

New submission from Roman Bolshakov: There's no code that closes read pipe(Process.sentinel) when a Process is joined. That creates issues in long running programs as the pipe's file descriptors are effectively leaked. -- components: Library (Lib) files: leak.py messages: 266598 nosy: