unknown error: Chrome failed to start: exited abnormally

[stephenson]

Hi Heroku
Over night my tests have started to fail (only on Heroku Pipeline) with the following error:

Selenium::WebDriver::Error::UnknownError: unknown error: Chrome failed to start: exited abnormally (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /app/.apt/usr/bin/google-chrome-stable is no longer running, so ChromeDriver is assuming that Chrome has crashed.) (Driver info: chromedriver=2.41.578700 (2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 4.4.0-1027-aws x86_64)

Nothing has changed in our setup and it seems like the only buildpack that has changed is this.

You have updated the main file, but not updated the changelog, how do I roll back and use the old version?

[Naveen7696]

Hi Heroku
I also got that same error

Selenium::WebDriver::Error::UnknownError:
unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /app/.apt/usr/bin/google-chrome-stable is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=2.41.578700 (2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 4.4.0-1027-aws x86_64)

[cimm]

Same here, Rails application using Heroku CI. Was working fine until a few hours ago:

 Failure/Error: page.set_rack_session(admin_id: admin.id)
 Selenium::WebDriver::Error::UnknownError:
   unknown error: Chrome failed to start: exited abnormally
     (unknown error: DevToolsActivePort file doesn't exist)
     (The process started from chrome location /app/.apt/usr/bin/google-chrome-stable is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
     (Driver info: chromedriver=2.41.578700(2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 4.4.0-1027-aws x86_64)

[rubendinho]

Also experiencing the same issue on Heroku CI.

Selenium::WebDriver::Error::UnknownError:
            unknown error: Chrome failed to start: exited abnormally
              (unknown error: DevToolsActivePort file doesn't exist)
              (The process started from chrome location /app/.apt/usr/bin/google-chrome-stable is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
              (Driver info: chromedriver=2.41.578700 (2f1ed5f9343c13f73144538f15c00b370eda6706),platform=Linux 4.4.0-1027-aws x86_64)

[jabrown85]

Is this still happening for you all? Can you try running a test with the no-cache option?

I saw this earlier but it resolved itself. I am wondering if there was a chrome release that caused this that was patched.

If you are still seeing it, can you post what heroku stack you are using?

[joseramonc]

@jabrown85 after re-run without cache, I'm not getting that error, however there are a few browser tests that are failing (they weren't failing before, and they are only failing at Heroku CI).

Stack is heroku-16 with buildpacks:

https://github.com/heroku/heroku-buildpack-google-chrome
https://github.com/heroku/heroku-buildpack-chromedriver
heroku/ruby

Any CI config was changed, so I'm not sure how to fix this. Is there something you suggest doing?

[nicolasmlv]

I have the same error. I reverted the commit in my fork and it works again (using heroku buildpacks:set https://github.com/nicolasmlv/heroku-buildpack-google-chrome#missinglibs)

What is the no-cache option?

I just tried to remove my reverted buildpack, then adding this one again, then heroku repo:purge_cache, then push empty commit, then heroku run bash, $ google-chrome -> and I still have /app/.apt/opt/google/chrome/chrome: error while loading shared libraries: libXcomposite.so.1: cannot open shared object file: No such file or directory

my buildpacks :

$ heroku buildpacks
=== myapp Buildpack URLs
1. heroku/ruby
2. https://github.com/heroku/heroku-buildpack-activestorage-preview
3. https://github.com/heroku/heroku-buildpack-google-chrome

[jabrown85]

@nicolasmlv by no cache I meant using the "Run again without cache" option from dashboard. You can also specify it via the cli: heroku ci:run --no-cache

[jabrown85]

If anyone is still having failures after now:

Is there anything consistent about the tests that are failing?
What options, if any, are you passing to chrome?
If it's consistent, can you replicate inside of heroku ci:debug?

Looking at the 'Chrome failed to start: exited abnormally' error and it seems to be pretty common over the last year. I wonder if chrome changed something in the same version that updated the dependencies that made it happen more often. If anyone can help narrow down the type of test that fails the most often, we can investigate further.

[rubendinho]

@jabrown85 I am no longer experiencing this problem. Thanks for the help!

[cimm]

Rerunning the build with the "Run Again Without Cache" option in the Heroku CI UI fixed the issue! 👍

[stephenarifin]

I am still having this issue. I am using this buildpack within my actual application for web scraping and I'm getting the error every time I try to launch the browser. It just started happening today with no changes in my code.

Running the CI with --no-cache is obviously not an option for me. Any advice please?

EDIT: Using @nicolasmlv new buildpack worked! Thanks for that fork. Would love for this issue to be addressed in master

[jabrown85]

@stephenarifin I believe master should be working for you. Switching back to the master will probably just work, since it was the switching of the buildpack that probably dropped the cache. If you get the error, you might also try the repo:purge_cache on that app.

[cmunozgar]

I am still having the same issue. I tried with @nicolasmlv buildpack and got the same error. I tried doing the repo:purge_cache with no success... I'm also using the https://github.com/heroku/heroku-buildpack-chromedriver buildpack. Is this 100% necessary to use the buildpack?

[erikaxel]

Same issue here. According to https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#chrome-headless-doesnt-launch
libxcomposite1 is a required dependency, but it is only included in the build phase for a heroku-16 stack. I did also do the full repo:purge_cache.