Puppeteer: Process exited with code {value}

The browser-management CLI’s child process exited nonzero.

Error message

Process exited with code {value}

{value} is replaced by the value shown in your error message.

How this error happens

The experimental browser bisector’s child process exited nonzero. A missing Python runtime, a helper failure or invalid test configuration can make the process fail.

The commands illustrate a project that intentionally uses browser bisection; no helper or test is supplied by this website.

npx @puppeteer/browsers bisect smoke \
    --good="$GOOD_CHROME_BUILD" \
    --bad="$BAD_CHROME_BUILD"

How to fix

For a download failure, restore trusted network access to the helper’s host. For a child-process failure, inspect its stderr, ensure the required runtime is present, and verify the smoke test before rerunning.

npm run smoke

npx @puppeteer/browsers bisect smoke \
    --good="$GOOD_CHROME_BUILD" \
    --bad="$BAD_CHROME_BUILD"

Things to keep in mind

This assumes your own project already has a smoke test and the environment variables contain valid Chrome build identifiers. The bisector downloads and runs a helper; it is not required for ordinary Puppeteer automation. A smoke test failure alone is not proof that the helper subprocess emitted this message.

All Puppeteer errors