Bug that occurs every once in a while

[kelhaji]

Great tool, this is so much better than WebLab! I have had one issue though, every once in a while I get the following error:

(node:55140) UnhandledPromiseRejectionWarning: Error: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
    at CDPSession.send (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/Connection.js:180:29)
    at ExecutionContext._evaluateInternal (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/ExecutionContext.js:107:44)
    at ExecutionContext.evaluate (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/ExecutionContext.js:48:23)
    at ExecutionContext.<anonymous> (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/helper.js:112:23)
    at DOMWorld.evaluate (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/DOMWorld.js:112:20)
  -- ASYNC --
    at Frame.<anonymous> (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/helper.js:111:15)
    at Page.evaluate (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/Page.js:860:43)
    at Page.<anonymous> (/Users/.../Desktop/weblab-runner/node_modules/puppeteer/lib/helper.js:112:23)
    at uploadContents (/Users/.../Desktop/weblab-runner/index.js:65:14)
    at async StatWatcher.<anonymous> (/Users/.../Desktop/weblab-runner/index.js:140:5)
(node:55140) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:55140) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Despite the error message given the page wasn't closed.