* Amnon <amno...@gmail.com> [220510 12:52]: > > I'm not sure why w.Write would freeze; is your process starting to swap > > and it is not really frozen but just taking a long time? Is it being > > killed by the kernel's out-of-memory monitor? > > In the OP's code, w.Write was writing a large amount of data to a pipe, > while nothing was reading from the other end. > This was the reason for the deadlock.
That makes sense. Ah, now, looking through https://groups.google.com/g/golang-nuts (I normally use email), I see a different thread to which I had not paid attention. ...Marvin -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/Ynqfy11tpIEiLsHv%40basil.wdw.
