Socket-child can be left orphaned on parent crash

[Julusian]

• I'm submitting a ...
  bug report

• Summary
  Attempt 3 Socket-child can be left orphaned on parent crash #30 Socket-child can be left orphaned on parent crash #40

Companion crashed a bunch of times at startup due to mismatch in natives api version.
I think a bunch of these aren't from crashes, but are from running via nodemon. Every time it restarts another child gets added

[Julusian]

The child has been rewritten to be a ThreadedClass which should be better at avoiding this, especially as it now runs as a worker thread when possible