Headless Chrome fails on new Chrome update 58.0.3029.81 - wrong launcher path (MAC)

[missbruni]

I had the launcher working for HeadlessChrome until the latest google update 58.0.3029.81 and I can see is because the path for the launcher is now incorrect.

karma.conf:

    browsers: ['HeadlessChrome'],

    customLaunchers: {
      HeadlessChrome: {
        base: 'Chrome',
        flags: ['--headless', '--disable-gpu', ' --remote-debugging-port=9222']
      }
    },

When trying to launch Chrome, the launcher tries to find the resources.pak inside the wrong folder (/Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/resources.pak).

I believe it must have changed with the update as is now located inside /Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/Resources/resources.pak

02 05 2017 14:36:42.952:INFO [launcher]: Trying to start Chrome again (2/2).
02 05 2017 14:36:43.113:ERROR [launcher]: Cannot start Chrome
[0502/143643.028018:ERROR:resource_bundle.cc(767)] Failed to load /Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/resources.pak
Some features may not be available.

I have only tested this with macOS Sierra 10.12.4, not sure about windows.

[missbruni]

For now I moved the resources.pak back to the launcher path to make it work again.

[zowers]

looks like an issue in chrome itself, see similar issue testem/testem#1117

[dpogue]

--headless is only supported in Chrome 59 and higher on Linux and macOS. Chrome 58 is not supported (although I seem to recall that it works on Linux).

Chrome 59 is currently in the beta channel.

[zowers]

@dpogue no, I have headless in 58

[dpogue]

Well, the flag exists, but you'll run into that resources.pkg error. It is only officially supported in Chrome 59 and up.

[rogeriopvl]

@missbruni when you mention latest update, do you mean latest google chrome update? or karma-chrome-launcher update?

Anyway this really sounds like it's unrelated with karma-chrome-launcher 🤔

[mgol]

We could probably leave this issue open for the next few weeks until Chrome 59 is released so that people don't open new ones. What do you think, @dignifiedquire?

[zowers]

@dpogue works fine in windows and linux

[missbruni]

@rogeriopvl I meant google update :)
It might not be a karma launcher issue but considering it relies on google to work and the new update stops supporting --headless in iOS because of the path I thought I needed to flag it so you guys are aware.

[wi-ski]

Im experiencing seg-faults in version 59 (beta) and 60 (canary)

[mgol]

@wi-ski On a Mac?

[wi-ski]

@mgol Yes. And on ubuntu 14 (heroku)

[cklab]

Throwing in some data points on local testing.

Browser definition:

customLaunchers: {
    "Chrome-headless": {
        base: 'Chrome',
        flags: ['--headless', '--disable-gpu', '--remote-debugging-port=9222', '--no-sandbox']
    }
}

Environment
karma-chrome-launcher: 2.1.1
Karma: 0.13.22
OS: OSX 10.11.6
Chrome: 58.0.3029.110

with karma.conf browser "Chrome-headless": ❌ fails with "cannot start" error
with karma.conf browser "Chrome": ✅

Updated chrome and ran same tests

Environment
karma-chrome-launcher: 2.1.1
Karma: 0.13.22
OS: OSX 10.11.6
Chrome: 59.0.3071.86

with karma.conf browser "Chrome-headless": ✅
with karma.conf browser "Chrome": ✅

[rogeriopvl]

I'm closing this due to inactivity. Please let me know if this is still an issue so we can reopen it.