FATAL:zygote_communication_linux.cc(254)] Cannot communicate with zygote
GlebObodovsky opened this issue · comments
Hello.
Thank you for the great work on serverless-chrome.
We use it on AWS Lambda, but sometimes it fails with:
FATAL:zygote_communication_linux.cc(254)] Cannot communicate with zygote
#0 0x000003b7633c <unknown>
#1 0x000003b014c0 <unknown>
#2 0x000004c0f472 <unknown>
#3 0x000004c15593 <unknown>
#4 0x000003ab0ef5 <unknown>
#5 0x000004bfeec8 <unknown>
#6 0x000003aa9d31 <unknown>
#7 0x000003b9745d <unknown>
#8 0x000003b974e8 <unknown>
#9 0x000003aea99a <unknown>
#10 0x7f96a06a30ba __libc_start_main
#11 0x00000242402a _start
Received signal 6
#0 0x000003b7633c <unknown>
#1 0x000003b75ea1 <unknown>
#2 0x7f96a16077e0 <unknown>
#3 0x7f96a06b5c20 __GI_raise
#4 0x7f96a06b70c8 __GI_abort
#5 0x000003b74cf5 <unknown>
#6 0x000003b01929 <unknown>
#7 0x000004c0f472 <unknown>
#8 0x000004c15593 <unknown>
#9 0x000003ab0ef5 <unknown>
#10 0x000004bfeec8 <unknown>
#11 0x000003aa9d31 <unknown>
#12 0x000003b9745d <unknown>
#13 0x000003b974e8 <unknown>
#14 0x000003aea99a <unknown>
#15 0x7f96a06a30ba __libc_start_main
#16 0x00000242402a _start
r8: 0000000000000000 r9: 00007fffc04088d0 r10: 0000000000000008 r11: 0000000000000246
r12: 00007fffc0409050 r13: 000000000000005c r14: 00007fffc0409058 r15: 00007fffc0409060
di: 0000000000000002 si: 00007fffc04088d0 bp: 00007fffc0408b20 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f96a06b5c20 sp: 00007fffc04088d0
ip: 00007f96a06b5c20 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
With parameters:
"--headless",
"--disable-dev-shm-usage",
"--ignore-certificate-errors",
"--no-sandbox",
"--hide-scrollbars",
"--disable-gpu",
"--single-process",
"--proxy-server=",
"--proxy-bypass-list=*",
"--print-to-pdf={outputFileName} "file://{htmlFilePath}""
What's more interesting, it occurs seldomly without any particular reason. At least, we were not able to reproduce it manually. It seems like it doesn't fail with the same input twice.
Can you help us with understanding of the root of that problem?
Zygote won't work in Serverless environments. Luckily there is the --no-zygote
parameter :-)