-
-
Notifications
You must be signed in to change notification settings - Fork 35.6k
"write after end" error when stdout was end()-edΒ #9403
Copy link
Copy link
Closed
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.processIssues and PRs related to the process subsystem.Issues and PRs related to the process subsystem.streamIssues and PRs related to the stream subsystem.Issues and PRs related to the stream subsystem.
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.processIssues and PRs related to the process subsystem.Issues and PRs related to the process subsystem.streamIssues and PRs related to the stream subsystem.Issues and PRs related to the stream subsystem.
Type
Fields
Give feedbackNo fields configured for issues without a type.
master, presumably all recent node major versionsstdout/stderrunexpectedly throw awrite after enderror whenend()has been called on them, even thoughend()throws it's own error indestroy()/destroySoon()overriding the usual destroy code which is innet.Socket. Since it overrides the destroy code, I don't think it should ever actually destroy the stream, which the error seems to indicate, but it appears to destroy it nonetheless.Try in the REPL:
cc @nodejs/streams