On Wed, 03 Aug 2016 12:23:32 -0700, jn...@jnthn.net wrote: > I can still reproduce it too; seems that occasionally the scheduler > starts too few threads (in fact, only one, and that is tied up with > the await, and so nothing processes the incoming message saying the > process ended).
The new scheduler merged a couple weeks back addresses this; added a test in S17-procasync/stress.t.
