Fixed a page crashed error

[possibly-not]

Added '--disable-dev-shm-usage', '--disable-gpu' into the puppeteer launch in order to fix a "(node:117132) UnhandledPromiseRejectionWarning: Error: Page crashed!" error I was constantly getting.

Thank you to puppeteer/puppeteer#1321 (comment) for the fix aha!
I have no knowledge of Javascript/Node but this seems to work for me so I would like to see if this helps others too.

[possibly-not]

Ah! Seems like I'm getting the original problem still. It's hard to reliably get as well which makes it annoying, I'm going to try what was recommended here puppeteer/puppeteer#3709 (comment) for the time being.

[yjaaidi]

Hi @Possibly-Matt! Thank you for your feedback and PR.
Do you have any more information concerning the error? Could that be a memory limit issue?
Let me know if you have any new info on the issue.

[possibly-not]

@yjaaidi thank you for the reply, I should've included the error! That's my fault, here it is.

(node:29369) UnhandledPromiseRejectionWarning: Error: Page crashed!
     at Page._onTargetCrashed (/home/myname/.config/yarn/global/node_modules/puppeteer/lib/Page.js:215:24)
     at CDPSession.<anonymous> (/home/myname/.config/yarn/global/node_modules/puppeteer/lib/Page.js:123:56)
     at CDPSession.emit (events.js:314:20)
     at CDPSession._onMessage (/home/myname/.config/yarn/global/node_modules/puppeteer/lib/Connection.js:200:12)
     at Connection._onMessage (/home/myname/.config/yarn/global/node_modules/puppeteer/lib/Connection.js:112:17)
     at WebSocket.<anonymous> (/home/myname/.config/yarn/global/node_modules/puppeteer/lib/WebSocketTransport.js:44:24)
     at WebSocket.onMessage (/home/myname/.config/yarn/global/node_modules/ws/lib/event-target.js:120:16)
     at WebSocket.emit (events.js:314:20)
    at Receiver.receiverOnMessage (/home/myname/.config/yarn/global/node_modules/ws/lib/websocket.js:789:20)
    at Receiver.emit (events.js:314:20)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:29369) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29369) [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.