SERVER-133871ClosedWon't Fix
Windows NamedPipeOutput leaks handle if writer thread creation fails
h2. Problem On Windows, {{NamedPipeOutput}} creates a valid pipe handle in its constructor but its destructor only calls CloseHandle() when the pipe is marked open. If the object is destroyed before open() succeeds, the handle is leaked. There are Windows and POSIX variants of {{NamedPipeOutput}}. Currently this code is only used in JavaScript and C++ tests. h2. Impact The handle remains open until the shell process exits. h2. Reproduction Context The issue is exposed when cal