This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
Close child pipes when child exits (+ test) #3031
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This essentially fixes #818: when a child process exits,
stdout
andstderr
are now closed.There seems to be a difference in behavior between Windows and Unix in this scenario. Even if a child process spawns a grandchild, on unix, when a child exits, the stdout/stderr pipes associated with it are broken so that parent process streams are closed automatically. On Windows, the pipes remain open until the grandchild exits.
The current implementation in node will wait for the streams to be closed before emitting the
exit
event (even though the child already exited).See discussion in joyent/libuv#343. It seems that the preferred solution is to make this fix at the node level instead of libuv.
The associated test (
simple/test-child-process-tree
) fails without this patch only on Windows.Contributed: @yosefd @saary