Exception in IPC call about h.pipes

[HavenDV]

Unfortunately, the bulk of the work on this library was done five years ago, and I didn’t really include any heavily loaded scenarios (although I wouldn’t say that your example is about a heavy load).
There are likely still some multi-threading issues at the library level that lead to this in rare cases, and it's best to create tests/benchmarks to identify this and fix it. The problem here is that my free time is quite limited right now and I can't give a clear time frame regarding this (for me it looks like a full 4-8 hour day of work testing and fixing this)
There's a small chance that it's all down to implementation at the system API level, but I wouldn't bet too much on it. Then the problem is more serious and we need to think about some pipe blocking between processes

[michalpaukert]

I am using this package for more then 1 year and this issue occured just recently on one of our virtual machines more then once. If you could give me a hint I could try to investigate.

[HavenDV]

The first step is to recreate the high load within a single test and get your problem replicated. Moreover, as I understand it, this behavior may be platform-specific and appear only on Windows (I mainly use macOS for work). You can help even if you just provide a PR with this test.
The second step is to find the problem. And here, if I had time, I would rewrite part of the code to use Dataflow(https://learn.microsoft.com/en-us/dotnet/standard/parallel-programming/dataflow-task-parallel-library)