I'm using processx to run several long-lived (i.e. weeks or months) processes on Windows 10, including capturing their output.

After a while, child processes end up in a state where I don't seem to be able to kill them (from the main process), they don't seem to be able to produce output and I end up with the following errors in the main process output:

An error occurred when writing to the named pipe. (system error 232, The pipe is being closed.
) @win/named_pipe.c:135 (processx_write_named_pipe)>
in process

I may well be doing something wrong. Any thoughts?