Release/v6.2.4

[stephen-palmer]

Fix a couple of high severity bugs:

• Automatically restart worker processes that die or are killed with SIGKILL (Manager process never restarts dead worker processes #94)
• Fixed a worker memory leak in the FS cache module (JavaScript heap out of memory #95)

[pullrequest]

✅ A review job has been created and sent to the PullRequest network.

---

Check the status or cancel PullRequest code review here - or - cancel by adding [!pr] to the title of the pull request.

[coveralls]

Coverage decreased (-1.1%) to 91.648% when pulling 3a5a111 on release/v6.2.4 into e320d5c on master.

[pullrequest]

I'm not sure if it's a great idea to restart something that was killed with SIGKILL, but I don't have all of the background information on the situation. I think from a code quality perspective, this looks good.

---

Was this helpful? Yes | No

[stephen-palmer]

As these are sub-processes and managed by the master node process, I think it's correct to allow the master to restart sub-processes killed externally via SIGKILL. Sending SIGKILL to the master will terminate the main process and all sub-processes immediately.