Docker: The display compositor is frequently crashing. Goodbye.
franz101 opened this issue · 24 comments
Hi,
I'm using a docker container with node:8-slim
and puppeteer 1.10.0. The container runs fine locally but on my Debian server I got the error Message:
gpu_data_manager_impl_private.cc(892)] The display compositor is frequently crashing. Goodbye.
I guess this might be chrome related and maybe caused through lack of memory.
.... Couldn't find anyone experiencing this error before.
Found a solution: Set chrome to stable
This seems to have broken again in latest stable. Google Chrome 73.0.3683.75
@rafael-paiva nope, just ended up downgrading to Chromium 72.0.3626.121.
I'm using headless Firefox so my tests are not blocked. @franz101 can we re-open this issue?
Can you guys share your docker container so that we can see this happenning locally?
This is happening for me on node:10-browsers and node:lts-browsers, pre-built docker images we're using in Circle: https://circleci.com/docs/2.0/circleci-images/#nodejs
These install Chrome @ 73.0.3683.75
Downgrading to node:10.14-browsers did the trick in the meantime (installed Chrome ~71)
@chrismllr do I understand correctly that it crashes for the Chrome that's bundled with the docker image? Does the Chromium version we bundle with Puppeteer crash the same way?
It has also happened similar crashes while running tests for our project.
https://circleci.com/gh/marp-team/marp-cli/1193
By using Chromium@74.0.3723.0 (r637110: Puppeteer v1.13.0 bundled version) instead Chrome@73.0.3683.75, it gets working well.
@aslushnikov Correct, it was the chrome in the prebuilt docker image. I may have jumped in based on a problem I was having elsewhere, but the bug seemed to be identical.
This seems to have broken again in latest stable.
Google Chrome 73.0.3683.75
`FROM node:8-slim
EXPOSE 3000 9229
#FROM node:latest
See https://crbug.com/795759
RUN 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-stable 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-init
RUN 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
RUN groupadd -r pptruser && useradd -r -g pptruser -G audio,video pptruser
&& mkdir -p /home/pptruser/Downloads && mkdir -p /home/pptruser/app/img
&& chown -R pptruser:pptruser /home/pptruser
RUN chown -R pptruser:pptruser /home/pptruser
RUN chmod -R 777 /home/pptruser/app/img
WORKDIR /home/pptruser/app
COPY . /home/pptruser/app
Install puppeteer so it's available in the container.
RUN npm i puppeteer
Add user so we don't need --no-sandbox.
RUN npm i -f
RUN npm install
Run everything after as non-privileged user.
USER pptruser
CMD npm run docker-start
`
I switched over to google-chrome-unstable which is 74.0... it works!
@rafael-paiva nope, just ended up downgrading to
Chromium 72.0.3626.121.
how to you downgrade in the docker file? It's working now using a different docker container:
https://github.com/buildkite/docker-puppeteer
but how do you set the chrome version to fixed?
Having the same issue when running in ubuntu container under windows (not docker).
google-chrome --version
Google Chrome 74.0.3729.22 dev
22 03 2019 12:09:12.354:ERROR [launcher]: ChromeHeadless crashed.
DevTools listening on ws://127.0.0.1:9222/devtools/browser/a9e949f6-bb7e-498f-a4d7-e2164c42fddc
[0322/120912.025646:FATAL:gpu_data_manager_impl_private.cc(897)] The display compositor is frequently crashing. Goodbye.
Failed to generate minidump.[0322/120912.337254:ERROR:broker_posix.cc(43)] Invalid node channel message
Im having the same issue on Google Chrome 74.0.3729.40 beta on WSL... Is this being worked by someone? should we create a bug report somewhere?
In my case I resolved it by adding option --disable-features=VizDisplayCompositor.
WSL-related issues are unrelated to Docker. Other than that, this seems to be fixed.
In my case I resolved it by adding option --disable-features=VizDisplayCompositor.
@dpdudek Man after a couple of hours of dealing with this problem that option saved my day. Thanks!
I have a quick question. Where can I check the list of features? I mean, how did you know that you have to disable that feature? It might be helpful in the future
@larzuk91 When I enabled verbose log
driver = webdriver.Chrome(executable_path=CHROME_DRIVER_PATH, options=chrome_options, service_args=["--verbose", "--log-path=/var/log/driver.log"])
then message from driver was "The display compositor is frequently crashing. Goodbye.". After that I found that message in gpu_data_manager_impl_private.cc. Looking in code I found that it was some inconsistency with disable gpu and VizDisplayCompositor feature in "if" expressions (I had disabled gpu by
--disable-gpu parameter). Somewhere else I found how to disable VizDisplayCompositor and it started working, so I stopped at that.
List of features is also available under chrome://flags, but now VizDisplayCompositor is not visible in my version of chrome ( 75.0.3770.80).
Ohh, it's clearer now. Thanks a lot for helping me understand what was happening. The funny part is by disabling that feature, it only crashes 3 times and after that it works
DevTools listening on ws://127.0.0.1:9222/devtools/browser/02600cca-cb6a-478f-be44-43b17ca624e6
[0605/111803.924207:WARNING:gpu_process_host.cc(1205)] The GPU process has crashed 1 time(s)
[0605/111804.278884:WARNING:gpu_process_host.cc(1205)] The GPU process has crashed 2 time(s)
[0605/111804.633481:WARNING:gpu_process_host.cc(1205)] The GPU process has crashed 3 time(s)
Not sure why but I'm happy that I can run my tests locally :)
In my case I resolved it by adding option --disable-features=VizDisplayCompositor.
THANK YOU!!
Ran into the same error with an electron app I've had installed forever that sporadically broke. Solved with --no-sandbox of all things which seems super weird considering it's a compositor issue.