BPO | [33191](https://bugs.python.org/issue33191) --- | :--- Nosy | @gpshead, @vstinner, @ned-deily, @zware, @pablogsal PRs | python/cpython#6315python/cpython#6331 Superseder | bpo-20104: expose posix_spawn(p) *Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.* Show more details GitHub fields: ```python assignee = None closed_at = created_at = labels = ['interpreter-core', '3.7', '3.8'] title = 'Refleak in posix_spawn' updated_at = user = 'https://github.com/zware' ``` bugs.python.org fields: ```python activity = actor = 'ned.deily' assignee = 'none' closed = True closed_date = closer = 'ned.deily' components = ['Interpreter Core'] creation = creator = 'zach.ware' dependencies = [] files = [] hgrepos = [] issue_num = 33191 keywords = ['patch'] message_count = 2.0 messages = ['314719', '314785'] nosy_count = 5.0 nosy_names = ['gregory.p.smith', 'vstinner', 'ned.deily', 'zach.ware', 'pablogsal'] pr_nums = ['6315', '6331'] priority = 'critical' resolution = 'duplicate' stage = 'resolved' status = 'closed' superseder = '20104' type = None url = 'https://bugs.python.org/issue33191' versions = ['Python 3.7', 'Python 3.8'] ```
Activity
zware commentedon Mar 30, 2018
There is a refleak in posix_spawn; see for example http://buildbot.python.org/all/#/builders/114/builds/53
The attached PR fixes it, but I am not confident that I did it correctly.
gpshead commentedon Apr 1, 2018
#6332 appears to address this.