Lighthouse throws "Error: Chrome could not be killed" when running check for multiple instances

[ericmustin]

Seeing Error pop up in my logs after running this with a few different instances after five or ten minutes:

2019-02-23 11:07:48 UTC | ERROR | (runner.go:289 in work) | Error running check custom_lighthouse: [{"message": "('', u\"events.js:173\\n      throw er; // Unhandled 'error' event\\n      ^\\n\\nError: read ECONNRESET\\n    at TCP.onStreamRead (internal/stream_base_commons.js:162:27)\\nEmitted 'error' event at:\\n    at Socket.socketErrorListener (_http_client.js:397:9)\\n    at Socket.emit (events.js:197:13)\\n    at emitErrorNT (internal/streams/destroy.js:82:8)\\n    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)\\n    at processTicksAndRejections (internal/process/next_tick.js:76:17)\\n\", 1)", "traceback": "Traceback (most recent call last):\n  File \"/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/base/checks/base.py\", line 387, in run\n    self.check(copy.deepcopy(self.instances[0]))\n  File \"/etc/datadog-agent/checks.d/custom_lighthouse.py\", line 24, in check\n    raise Exception(json_string, error_message, exit_code)\nException: ('', u\"events.js:173\\n      throw er; // Unhandled 'error' event\\n      ^\\n\\nError: read ECONNRESET\\n    at TCP.onStreamRead (internal/stream_base_commons.js:162:27)\\nEmitted 'error' event at:\\n    at Socket.socketErrorListener (_http_client.js:397:9)\\n    at Socket.emit (events.js:197:13)\\n    at emitErrorNT (internal/streams/destroy.js:82:8)\\n    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)\\n    at processTicksAndRejections (internal/process/next_tick.js:76:17)\\n\", 1)\n"}]

2019-02-23 11:09:11 UTC | ERROR | (runner.go:289 in work) | Error running check custom_lighthouse: [{"message": "('', u\"Unhandled Rejection. Reason: Error: Chrome could not be killed kill ESRCH\\nCouldn't quit Chrome process. Error: Chrome could not be killed kill ESRCH\\nevents.js:173\\n      throw er; // Unhandled 'error' event\\n      ^\\n\\nError: connect ECONNREFUSED 127.0.0.1:45429\\n    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1083:14)\\nEmitted 'error' event at:\\n    at Socket.socketErrorListener (_http_client.js:397:9)\\n    at Socket.emit (events.js:197:13)\\n    at emitErrorNT (internal/streams/destroy.js:82:8)\\n    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)\\n    at processTicksAndRejections (internal/process/next_tick.js:76:17)\\n\", 1)", "traceback": "Traceback (most recent call last):\n  File \"/opt/datadog-agent/embedded/lib/python2.7/site-packages/datadog_checks/base/checks/base.py\", line 387, in run\n    self.check(copy.deepcopy(self.instances[0]))\n  File \"/etc/datadog-agent/checks.d/custom_lighthouse.py\", line 24, in check\n    raise Exception(json_string, error_message, exit_code)\nException: ('', u\"Unhandled Rejection. Reason: Error: Chrome could not be killed kill ESRCH\\nCouldn't quit Chrome process. Error: Chrome could not be killed kill ESRCH\\nevents.js:173\\n      throw er; // Unhandled 'error' event\\n      ^\\n\\nError: connect ECONNREFUSED 127.0.0.1:45429\\n    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1083:14)\\nEmitted 'error' event at:\\n    at Socket.socketErrorListener (_http_client.js:397:9)\\n    at Socket.emit (events.js:197:13)\\n    at emitErrorNT (internal/streams/destroy.js:82:8)\\n    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)\\n    at processTicksAndRejections (internal/process/next_tick.js:76:17)\\n\", 1)\n"}]

Unsure what the issue is, maybe this would be resolved by moving over to use lighthouse-batch instead of lighthouse https://www.npmjs.com/package/lighthouse-batch