search

heroku / heroku-buildpack-google-chrome

Run (headless) Google Chrome on Heroku
296 stars 365 forks source link

Cannot start Chrome error #62

Closed gwvt closed 5 years ago

gwvt commented 6 years ago

Heroku CI tests with Karma and Chrome on a review app stopped working, with this output to the test log:

20 09 2018 13:08:41.460:ERROR [launcher]: Cannot start Chrome

    /app/.apt/opt/google/chrome/chrome: symbol lookup error: /app/.apt/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0: undefined symbol: g_log_structured_standard

20 09 2018 13:08:41.460:ERROR [launcher]: Chrome stdout:

20 09 2018 13:08:41.462:ERROR [launcher]: Chrome stderr: /app/.apt/opt/google/chrome/chrome: symbol lookup error: /app/.apt/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0: undefined symbol: g_log_structured_standard

The solution I finally found is to run the tests without cache. Can this issue be fixed, or can a note be added to the test log and/or documentation to spare others a trip into the rabbit hole? Thanks.

lancedikson commented 6 years ago

Run into exactly the same problem:

Built project successfully. Stored in "/app/tmp/class-tests_dist-gOBRymlO.tmp".
not ok 1 Chrome - error
    ---
        message: >
            Error: Browser exited unexpectedly
            Non-zero exit code: 127
            Stderr: 
             /app/.apt/opt/google/chrome/chrome: symbol lookup error: /app/.apt/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0: undefined symbol: g_log_structured_standard

        Log: |
            { type: 'error', text: 'Error: Browser exited unexpectedly' }
            { type: 'error', text: 'Non-zero exit code: 127' }
            { type: 'error',
              text: '/app/.apt/opt/google/chrome/chrome: symbol lookup error: /app/.apt/usr/lib/x86_64-linux-gnu/libatk-1.0.so.0: undefined symbol: g_log_structured_standard\n' }
    ...
1..1

It's an Ember.js project, the test runner is testem and we'd been successfully using this buildpack until Sep 13. Tried switching to the beta channel, doesn't help. cc @allinne

lancedikson commented 6 years ago

Ok, it's somehow fixed by using a no-cache rerun ¯_(ツ)_/¯

edmorley commented 5 years ago

It sounds like this was a temporary caching issue, so closing this out for now. For anyone else seeing this, reset the CI cache use the "Run again without cache" option in the dashboard.