question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sandbox Failure in PDF Generation

See original GitHub issue

decktape: 2.8.9 chromium: 69.0.3497.100 (Official Build) Arch Linux (64-bit) node: 8.9.4

node /path/to/slides/node_modules/decktape/decktape.js -p 1000 file:///path/to/slides/.tmp/pdf/presentation.html pdf/presentation.pdf
Error: Failed to launch chrome!
[0928/161849.922445:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x55741f07c8ec base::debug::StackTrace::StackTrace()
#1 0x55741eff8200 logging::LogMessage::~LogMessage()
#2 0x5574204eb4f0 service_manager::ZygoteHostImpl::Init()
#3 0x55741ecbf54e content::ContentMainRunnerImpl::Initialize()
#4 0x55741ecf2eb8 service_manager::Main()
#5 0x55741ecbdd91 content::ContentMain()
#6 0x5574231c597d headless::(anonymous namespace)::RunContentMain()
#7 0x5574231c5a08 headless::HeadlessBrowserMain()
#8 0x55741ecf04ab headless::HeadlessShellMain()
#9 0x55741d0b51ac ChromeMain
#10 0x7f056f5e5223 __libc_start_main
#11 0x55741d0b502a _start

Received signal 6
#0 0x55741f07c8ec base::debug::StackTrace::StackTrace()
#1 0x55741f07c451 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x7f05728413c0 <unknown>
#3 0x7f056f5f8d7f __GI_raise
#4 0x7f056f5e3672 __GI_abort
#5 0x55741f07b275 base::debug::BreakDebugger()
#6 0x55741eff8669 logging::LogMessage::~LogMessage()
#7 0x5574204eb4f0 service_manager::ZygoteHostImpl::Init()
#8 0x55741ecbf54e content::ContentMainRunnerImpl::Initialize()
#9 0x55741ecf2eb8 service_manager::Main()
#10 0x55741ecbdd91 content::ContentMain()
#11 0x5574231c597d headless::(anonymous namespace)::RunContentMain()
#12 0x5574231c5a08 headless::HeadlessBrowserMain()
#13 0x55741ecf04ab headless::HeadlessShellMain()
#14 0x55741d0b51ac ChromeMain
#15 0x7f056f5e5223 __libc_start_main
#16 0x55741d0b502a _start
  r8: 0000000000000000  r9: 00007ffcbc4a86b0 r10: 0000000000000008 r11: 0000000000000246
 r12: 00007ffcbc4a8ed8 r13: 0000000000000161 r14: 00007ffcbc4a8ee0 r15: 00007ffcbc4a8ee8
  di: 0000000000000002  si: 00007ffcbc4a86b0  bp: 00007ffcbc4a8900  bx: 0000000000000006
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f056f5f8d7f  sp: 00007ffcbc4a86b0
  ip: 00007f056f5f8d7f 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.


TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md

    at onClose (/path/to/slides/node_modules/puppeteer/lib/Launcher.js:333:14)
    at Interface.helper.addEventListener (/path/to/slides/node_modules/puppeteer/lib/Launcher.js:322:50)
    at emitNone (events.js:111:20)
    at Interface.emit (events.js:208:7)
    at Interface.close (readline.js:370:8)
    at Socket.onend (readline.js:149:10)
    at emitNone (events.js:111:20)
    at Socket.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1055:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)

If I add --no-sandbox to the list on line 207, it will work as expected. However, I don’t like living dangerously and it should function without disabling the sandbox.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
astefanutticommented, Mar 17, 2019

There has been a change in the way you can pass argument to Chromium. For instance, to disable sandboxing, you should now be using --chrome-arg=--no-sandbox. That being said, relying on a distro installed Chromium instance is a good solution too, maybe worth documenting…

0reactions
allsey87commented, Mar 17, 2019

That makes sense. Passing the --no-sandbox wasn’t making any difference for me. I kept getting the error reported above.

Error: Failed to launch chrome! [0928/161849.922445:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

I think using an existing/working chrome installation is good work around for the time being. That’s why I added the above info.

Read more comments on GitHub >

github_iconTop Results From Across the Web

PDF page export fails with: SandboxCrashedException ...
Cause. The PDF export is processed by Confluence in a separated Java process to avoid problems with the main Confluence process. The Sandbox...
Read more >
Failed to generated PDF · Issue #20 · simonhaenisch/md-to-pdf
Hi! When doign md2pdf HowToMarkdown.md. I get and error when generating the PDF, I read the Troubleshooting link but I couldn't find what...
Read more >
Visualforce renderAs PDF sandbox - production difference ...
We have a visualforce page rendered as PDF that uses some tables and css for simple styling, the problem is that in the...
Read more >
When Your Sandbox Fails - Dark Reading
Emotet, Bebloh, and PDF phishing attacks are worrisome for one very good reason. They use sophisticated — ingenious, really — techniques to ...
Read more >
Convert to PDF Not Working - Power Platform Community
I'm building a very simple flow and the Convert File continues to fail no matter what changes/modifications I make to my flow.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found