Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.7] bpo-35182: fix communicate() crash after child closes its pipes (GH-18117) #18151

Merged
merged 1 commit into from Jan 23, 2020

Conversation

@alpire
Copy link
Contributor

alpire commented Jan 23, 2020

When communicate() is called in a loop, it crashes when the child process
has already closed any piped standard stream, but still continues to be running

Co-authored-by: Andriy Maletsky andriy.maletsky@gmail.com.
(cherry picked from commit d3ae95e)

Co-authored-by: Alex Rebert alex@forallsecure.com

https://bugs.python.org/issue35182

Automerge-Triggered-By: @gpshead

…GH-17020) (GH-18117)

When communicate() is called in a loop, it crashes when the child process
has already closed any piped standard stream, but still continues to be running

Co-authored-by: Andriy Maletsky <andriy.maletsky@gmail.com>.
(cherry picked from commit d3ae95e)

Co-authored-by: Alex Rebert <alex@forallsecure.com>
@miss-islington miss-islington merged commit 61b3484 into python:3.7 Jan 23, 2020
10 checks passed
10 checks passed
Docs
Details
Windows (x86)
Details
Windows (x64)
Details
macOS
Details
Ubuntu
Details
Azure Pipelines PR #20200123.46 succeeded
Details
bedevere/issue-number Issue number 35182 found
Details
bedevere/maintenance-branch-pr Valid maintenance branch PR title.
bedevere/news News entry found in Misc/NEWS.d
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.