[issue39535] multiprocessing.Process file descriptor resource leak

[Robert Pierce]

Robert Pierce  added the comment:

It appears as if the problem is the sentinel FIFO opened by (for example) 
multiprocessing.popen_fork.Popen._launch(). It registers a finalization class 
to close the sentinel on garbage collection. Instead, it should be closed in 
poll() or wait() when the child process is reaped and known to be dead. The 
sentinel serves no purpose after the child is reaped, and waiting till garbage 
collection means that programs forking large numbers of processes cannot 
control file descriptor utilization.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39535] multiprocessing.Process file descriptor resource leak

[Robert Pierce]

New submission from Robert Pierce :

multiprocessing.Process opens a FIFO to the child. This FIFO is not documented 
the the Process class API and it's purpose is not clear from the documentation. 
It is a minor documentation bug that the class creates non-transparent resource 
utilization.

The primary behavioral bug is that incorrect handling of this FIFO creates a 
resource leak, since the file descriptor is not closed on join(), or even when 
the parent Process object goes out of scope.

The effect of this bug is that programs generating large numbers of Process 
objects will hit system resource limits of open file descriptors.

--
assignee: docs@python
components: Documentation, Library (Lib)
files: proc_test.py
messages: 361273
nosy: Robert Pierce, docs@python
priority: normal
severity: normal
status: open
title: multiprocessing.Process file descriptor resource leak
type: resource usage
versions: Python 3.6
Added file: https://bugs.python.org/file48878/proc_test.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com