handx-lambda: "Navigation failed because browser has disconnected"

[rcmiller]

Sometimes the lambda function fails with this error:

{
  "errorType": "Error",
  "errorMessage": "Navigation failed because browser has disconnected!",
  "trace": [
    "Error: Navigation failed because browser has disconnected!",
    "    at /opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/LifecycleWatcher.js:51:147",
    "    at /opt/nodejs/node_modules/puppeteer-core/lib/cjs/vendor/mitt/src/index.js:47:62",
    "    at Array.map (<anonymous>)",
    "    at Object.emit (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/vendor/mitt/src/index.js:47:43)",
    "    at CDPSession.emit (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/EventEmitter.js:72:22)",
    "    at CDPSession._onClosed (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:247:14)",
    "    at Connection._onClose (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:128:21)",
    "    at WebSocket.<anonymous> (/opt/nodejs/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WebSocketTransport.js:17:30)",
    "    at WebSocket.onClose (/opt/nodejs/node_modules/ws/lib/event-target.js:129:16)",
    "    at WebSocket.emit (events.js:314:20)"
  ]
}

Which often leaves the disk full on the lambda function execution instance (perhaps it is caused by disk-full?), and the lambda function stops working until it has been redeployed (or until the execution instance has been garbage-collected from lack of use).