Serverless-chrome: ps.lookup doesn't work on AWS Lambda

[schickling]

You're using ps.loopup() from the ps-node package. However ps l doesn't seem to work on AWS Lambda. Is it really needed here?

I ran a few tests here:

[adieuadieu]

@schickling yea; you're right. I was trying to use ps-node to detect if Chrome was already running, but like you noticed, it doesn't work on lambda. I've removed ps-node from my refactor, but will close this Issue only after that's been pushed. See here for some in-code commentary.

Should add: I expect to finish the second and third checklist items in #4 by late next week—will include removal of ps-node

[adieuadieu]

By the way: Love Graphcool! Pretty stoked I got a Star from it's founder! 😄

[schickling]

Thanks so much @adieuadieu 🙂

You're doing great work with this serverless package. We'll use it for our build-time pre-rendering (in next version of prep)!

[bluepeter]

Looking forward to getting the rework! We need you :) https://news.ycombinator.com/item?id=14105489

[adieuadieu]

@schickling I noticed something which doesn't quite make sense to me:

ps l doesn't work on lambda. However, ps lx does. 😖 Huh?

Also, since March 26th, ps-node now uses ps lx by default—so now ps.lookup() also works.

_However_ Chrome behaves oddly in between innovations. It'll run across a few invocations, and then the process will randomly zombie:

1st invocation:

2017-05-03T08:21:23.897Z    7d66b110-2fd9-11e7-abd1-0fa82bf09592    ps lx
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
4 483 1 0 20 0 795104 35316 ep_pol Ssl ? 0:00 /var/lang/bin/node --max-old-space-size=1229 --max-semi-space-size=76 --max-executable-size=153 --expose-gc /var/runtime/node_modules/awslambda/index.js
0 483 12 1 20 0 115084 1612 - R ? 0:00 ps lx

2nd invocation:

2017-05-03T08:21:37.104Z    869a5830-2fd9-11e7-9483-9ff7caf0dfb8    ps lx
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
4 483 1 0 20 0 1137084 49408 ep_pol Ssl ? 0:00 /var/lang/bin/node --max-old-space-size=1229 --max-semi-space-size=76 --max-executable-size=153 --expose-gc /var/runtime/node_modules/awslambda/index.js
0 483 14 1 20 0 1159348 143396 ep_pol Ssl ? 0:01 /var/task/headless-chrome/headless_shell --headless --disable-gpu --window-size=1280x1696 --no-sandbox --user-data-dir=/tmp/user-data --hide-scrollbars --enable-logging --log-level=0 --v=99 --single-process --data-path=/tmp/data-path --ignore-certificate-errors --homedir=/tmp --disk-cache-dir=/tmp/cache-dir --remote-debugging-port=9222
1 483 16 14 20 0 0 0 exit Z ? 0:00 [headless_shell] <defunct>
0 483 49 1 20 0 115076 1640 - R ? 0:00 ps lx

3rd, 4th, 5th invocation:

2017-05-03T08:21:44.045Z    8abcb102-2fd9-11e7-9955-05d484a94301    ps lx
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
4 483 1 0 20 0 1206364 52440 ep_pol Ssl ? 0:00 /var/lang/bin/node --max-old-space-size=1229 --max-semi-space-size=76 --max-executable-size=153 --expose-gc /var/runtime/node_modules/awslambda/index.js
0 483 14 1 20 0 1221284 202544 ep_pol Ssl ? 0:01 /var/task/headless-chrome/headless_shell --headless --disable-gpu --window-size=1280x1696 --no-sandbox --user-data-dir=/tmp/user-data --hide-scrollbars --enable-logging --log-level=0 --v=99 --single-process --data-path=/tmp/data-path --ignore-certificate-errors --homedir=/tmp --disk-cache-dir=/tmp/cache-dir --remote-debugging-port=9222
1 483 16 14 20 0 0 0 exit Z ? 0:00 [headless_shell] <defunct>
0 483 54 1 20 0 115080 1640 - R ? 0:00 ps lx

6th invocation:

2017-05-03T08:23:07.546Z    bc762f22-2fd9-11e7-a839-cf7444a4c378    ps lx
F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND
4 483 1 0 20 0 1208000 54308 ep_pol Ssl ? 0:00 /var/lang/bin/node --max-old-space-size=1229 --max-semi-space-size=76 --max-executable-size=153 --expose-gc /var/runtime/node_modules/awslambda/index.js
0 483 14 1 20 0 0 0 exit Zsl ? 0:03 [headless_shell] <defunct>
1 483 16 14 20 0 0 0 exit Z ? 0:00 [headless_shell] <defunct>
0 483 65 1 20 0 115080 1672 - R ? 0:00 ps lx

[kzawadka]

@adieuadieu I was also getting numerous headless_shell zombies. Using the --no-zygote flag solved the issue for me.

[adieuadieu]

Thanks for the tip, @kzawadka!