E/launcher-未知错误:Chrome无法启动:在无头模式下崩溃



面临以下错误

  • 谷歌浏览器-67.0
  • chromedriver-chromedriver2.40
  • 硒独立-硒服务器-标准-3.12.0.jar
  • linux-CentOS linux 7.3版
  • 量角器-5.1.2
  • Nodejs-v6.14.2

配置

chrome: {
seleniumAddress: 'http://localhost:4444/wd/hub',
directConnect: true,
browserName: 'chrome',
chromeOptions:{
args: ['--headless','--disable-gpu','--disable-dev-shm-usage','--no-sandbox','window-size=1024,768']
}

10:37:07.923〔10:37:07〕I/launcher-运行1个WebDriver实例10:37:07.923[10:37:07]I/hosted-使用位于http://localhost:4444/wd/hub10:38:09.409[10:38:09]E/launcher-未知错误:Chrome无法启动:崩溃10:38:09.409(驱动程序信息:chromedriver=2.40.565383(76257d1ab79276b2d53ee976b2c3e3b9f335cde7),平台=Linux 3.10.0-514.26.2.el7.x86_64 x86_66)(警告:服务器未提供任何堆栈争用信息)10:38:09.409命令持续时间或超时:60.39秒10:38:09.409构建信息:版本:"3.12.0",修订:"7c6e0b3",时间:"2018-05-08T15:15:08.936Z"10:38:09.409系统信息:主机:"sigmagoagt-po-a1p.sys.comcast.net",ip:"147.191.72.189",os.name:"Linux",os.arch:"amd64",os.version:"3.10.0-514.26.2.el7.x86_64",java.version:"1.8.0_40"10:38:09.410驱动程序信息:驱动程序版本:未知10:38:09.410[10:38:09]E/launcher-WebDriverError:未知错误:Chrome无法启动:崩溃10:38:09.410(驱动程序信息:chromedriver=2.40.565383(76257d1ab79276b2d53ee976b2c3e3b9f335cde7),平台=Linux 3.10.0-514.26.2.el7.x86_64 x86_66)(警告:服务器未提供任何堆栈争用信息)10:38:09.410命令持续时间或超时:60.39秒10:38:09.410构建信息:版本:"3.12.0",修订:"7c6e0b3",时间:"2018-05-08T15:15:08.936Z"10:38:09.411系统信息:主机:"sigmagoagt-po-a1p.sys.comcast.net",ip:"147.191.72.189",os.name:"Linux",os.arch:"amd64",os.version:"3.10.0-514.26.2.el7.x86_64",java.version:"1.8.0_40"10:38:09.411驱动程序信息:驱动程序版本:未知10:38:09.411在WebDriverError上(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/selement-webdriver/lib/error.js:27:5)10:38:09.411在Object.checkLegacyResponse(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/selement-webdriver/lib/error.js:505:15)上午10:38:09.411在parseHttpResponse(/app/go-agent1/prints/UI Automation Testing/web/client-portal/node_modules/selement-webdriver/lib:http.js:509:13)10:38:09.412在doSend.then.response(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/selenium webdriver/lib:http.js:440:13)10:38:09.412正在进行中_tickCallback(internal/process/next_tick.js:109:7)10:38:09.412发件人:任务:WebDriver.createSession()上午10:38:09.412在Function.createSession(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/selenium webdriver/lib/webdriver.js:77:24)上午10:38:09.412在Function.createSession(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/selement-webdriver/chrome.js:709:29)10:38:09.412在createDriver上(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/selement-webdriver/index.js:167:33)10:38:09.412在Builder.build(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/selenium webdriver/index.js:623:16)10:38:09.413在Hosted.getNewDriver(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/decurator/lib/driverProviders/driverProvider.ts:60:29)10:38:09.413在Runner.createBrowser(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/decurator/lib/Runner.ts:225:39)10:38:09.413,时间:q.then(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/decurator/lib/runner.ts:391:27)10:38:09.413 at _fullived(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/dexactor/node_modules/q/q.js:834:54)10:38:09.413在self.promiseDispatch.done(/app/go-agent1/pipelines/UI Automation Testing/web/client-portal/node_modules/decurator/node_modules/q/q.js:863:30)10:38:09.413在Promise.Promise.dispatch(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/practor/node_modeles/q/q.js:796:13)10:38:09.1414,网址:/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/practor/node_modules/q/q.js:556:4910:38:09.1414在runSingle上(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/dexactor/node_modules/q/q.js:137:13)上午10:38:09.1414(/app/go-agent1/pelines/UI Automation Testing/web/client-portal/node_modules/dexactor/node_modules/q/q.js:125:13)10:38:09.1414在_combinedTickCallback(internal/process/next_tick.js:73:7)上午10:38:09.1414_tickCallback(internal/process/next_tick.js:104:9)

您可以使用selenium服务器运行测试,也可以直接在浏览器上运行测试。您应该删除其中一个:

seleniumAddress: 'http://localhost:4444/wd/hub',

directConnect: true,

在centOS机器中卸载并重新安装Chrome解决了这个问题。遵循了"中提供的安装程序https://intoli.com/blog/installing-google-chrome-on-centos/".谢谢。

最新更新