zepumph
commented
2 years ago I can reproduce this on bayes with another script that uses perennial's puppeteerLoad:
( async () => {
const puppeteerLoad = require( process.cwd() + '/../perennial/js/common/puppeteerLoad.js' );
const error = await puppeteerLoad( 'https://www.google.com', {
waitAfterLoad: 0
} );
console.log( error );
} )();
```
[phet-admin@bayes aqua]$ node ~/puppeteerTemp.js
(node:52841) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
[0523/101722.377058:FATAL:zygote_host_impl_linux.cc(174)] Check failed: process.IsValid(). Failed to launch zygote process
#0 0x560f2a46f469 base::debug::CollectStackTrace()
#1 0x560f2a3d5f33 base::debug::StackTrace::StackTrace()
#2 0x560f2a3e8d50 logging::LogMessage::~LogMessage()
#3 0x560f2a3e990e logging::LogMessage::~LogMessage()
#4 0x560f284a9b08 content::ZygoteHostImpl::LaunchZygote()
#5 0x560f29f83a30 content::(anonymous namespace)::LaunchZygoteHelper()
#6 0x560f27b086cb content::ZygoteCommunication::Init()
#7 0x560f27b08cd4 content::CreateGenericZygote()
#8 0x560f29f82e95 content::ContentMainRunnerImpl::Initialize()
#9 0x560f29f80eb9 content::RunContentProcess()
#10 0x560f29f8100e content::ContentMain()
#11 0x560f29fdbfca headless::(anonymous namespace)::RunContentMain()
#12 0x560f29fdbcd5 headless::HeadlessShellMain()
#13 0x560f26bcd668 ChromeMain
#14 0x7fa02e5da555 __libc_start_main
#15 0x560f26bcd4aa _start
Received signal 6
#0 0x560f2a46f469 base::debug::CollectStackTrace()
#1 0x560f2a3d5f33 base::debug::StackTrace::StackTrace()
#2 0x560f2a46ef71 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7fa032d57630 (/usr/lib64/libpthread-2.17.so+0xf62f)
#4 0x7fa02e5ee387 __GI_raise
#5 0x7fa02e5efa78 __GI_abort
#6 0x560f2a46e1f5 base::debug::BreakDebuggerAsyncSafe()
#7 0x560f2a3e9221 logging::LogMessage::~LogMessage()
#8 0x560f2a3e990e logging::LogMessage::~LogMessage()
#9 0x560f284a9b08 content::ZygoteHostImpl::LaunchZygote()
#10 0x560f29f83a30 content::(anonymous namespace)::LaunchZygoteHelper()
#11 0x560f27b086cb content::ZygoteCommunication::Init()
#12 0x560f27b08cd4 content::CreateGenericZygote()
#13 0x560f29f82e95 content::ContentMainRunnerImpl::Initialize()
#14 0x560f29f80eb9 content::RunContentProcess()
#15 0x560f29f8100e content::ContentMain()
#16 0x560f29fdbfca headless::(anonymous namespace)::RunContentMain()
#17 0x560f29fdbcd5 headless::HeadlessShellMain()
#18 0x560f26bcd668 ChromeMain
#19 0x7fa02e5da555 __libc_start_main
#20 0x560f26bcd4aa _start
r8: 0000000000000000 r9: 0000000000000300 r10: 0000000000000008 r11: 0000000000000202
r12: 00001b2600314140 r13: 00001b2600314158 r14: 00001b2600314150 r15: 00001b2600221400
di: 000000000000ce76 si: 000000000000ce76 bp: 00007ffec79adcd0 bx: 00007ffec79ae510
dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007ffec79adb98
ip: 00007fa02e5ee387 efl: 0000000000000202 cgf: aaaa000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
at onClose (/data/share/phet/continuous-quick-server/perennial/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20)
at ChildProcess. (/data/share/phet/continuous-quick-server/perennial/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:232:79)
at ChildProcess.emit (events.js:327:22)
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:52841) 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:52841) [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.
[phet-admin@bayes aqua]$
mattpen
This begain at 2am this morning. I cannot reproduce locally with
grunt quick-server, and a restart of the CTQ didn't fix it.