Puppeteer Error: Protocol error (Page.captureScreenshot): Target closed
I can provide you with a solution
FROM node:8-slim# See https://crbug.com/795759RUN apt-get update && apt-get install -yq libgconf-2-4# Install latest chrome dev package and fonts to support major charsets (Chinese, Japanese, Arabic, Hebrew, Thai and a few others)# Note: this installs the necessary libs to make the bundled version of Chromium that Puppeteer# installs, work.RUN apt-get update && apt-get install -y wget --no-install-recommends \ && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \ && sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' \ && apt-get update \ && apt-get install -y google-chrome-unstable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst ttf-freefont \ --no-install-recommends \ && rm -rf /var/lib/apt/lists/* \ && apt-get purge --auto-remove -y curl \ && rm -rf /src/*.deb# It's a good idea to use dumb-init to help prevent zombie chrome processes.ADD https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 /usr/local/bin/dumb-initRUN chmod +x /usr/local/bin/dumb-init# Uncomment to skip the chromium download when installing puppeteer. If you do,# you'll need to launch puppeteer with:# browser.launch({executablePath: 'google-chrome-unstable'})# ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true# Install puppeteer so it's available in the container.RUN npm i puppeteer# Add user so we don't need --no-sandbox.RUN groupadd -r pptruser && useradd -r -g pptruser -G audio,video pptruser \ && mkdir -p /home/pptruser/Downloads \ && chown -R pptruser:pptruser /home/pptruser \ && chown -R pptruser:pptruser /node_modules# Run everything after as non-privileged user.USER pptruserENTRYPOINT ["dumb-init", "--"]CMD ["google-chrome-unstable"]
Here is the best mirror I have found so far for google-chrome-stable for RPM-based systems.
Your issue is not reproducible. It works on my Centos 7, your Mac environment, so it seems to be a problem with the Docker configuration and not with the code. Possible problems:
- Used docker storage driver:
aufs
can be a problem, especially for older kernels and write/delete operations in the container; if it is possible try defaultoverlay2
- Used security profiles:
apparmor
andseccomp
are enabled, you may try to run with--security-opt seccomp=unconfined
and checkdmesg
, maybe security is blocking something
I am able to replicate this issue.
Here is my code
browser = await puppeteer.launch({ defaultViewport:{width:1920,height:6000}, headless: true, executablePath: await chromium.executablePath, args: chromium.args, ignoreDefaultArgs: ["--hide-scrollbars"], });let siteName = urlArray[urlIndex].split('://')[1]; const page = await browser.newPage(); await page.goto(urlArray[urlIndex], { waitUntil: ['domcontentloaded', 'networkidle0', 'networkidle2'], }); const buffer = await page.screenshot({ clip: { x: 0, y: 0, width:1920, height: 6000} }); result = await page.title();
Error
START RequestId: 51ec6b89-6c49-408d-95e1-f09492e1ecee Version: $LATEST2021-06-04T14:12:05.738Z 51ec6b89-6c49-408d-95e1-f09492e1ecee ERROR Error: Navigation failed because browser has disconnected!at CDPSession.LifecycleWatcher._eventListeners.helper.addEventListener (/opt/nodejs/node_modules/puppeteer-core/lib/LifecycleWatcher.js:46:107)at CDPSession.emit (events.js:198:13)
OR
Error: Protocol error (Page.captureScreenshot): Target closed
SolutionI was facing issue because of the screenshot height and width. My page is too long so I need to increase height of screenshot to 6000 which caused browser disconnection or protocol error. Moreover, I was using the same browser object to take screenshot of 4 websites which was causing the above issue.
So, I re-initialized the browser object before taking the screenshot like this:
for (let urlIndex = 0; urlIndex < urlArray.length; urlIndex++) { try { browser = await puppeteer.launch({ defaultViewport:{width:1920,height:6000}, headless: true, executablePath: await chromium.executablePath, args: chromium.args, ignoreDefaultArgs: ["--hide-scrollbars"], });
It resolved my issue.