Calling `close` inline within the loop seems to work fine and produces the expected result. I'm guessing that the implementation is somehow in a deadlock, or is just not designed to handle a disconnection while waiting on data. Whatever the case, it seems to be impossible to disconnect a socket without making all `asyncnet` procs hang.
- [asyncnet] Difference between a natural socket close and close(As... termer
- [asyncnet] Difference between a natural socket close and clo... termer