Issue metadata
Sign in to add a comment
|
Latest stable release of Google Chrome segmentation faults when running --headless.
Reported by
trey.cor...@socrata.com,
Apr 20 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Steps to reproduce the problem: /Applications » brew cask install google-chrome ==> Satisfying dependencies complete ==> Downloading https://dl.google.com/chrome/mac/stable/GGRO/googlechrome.dmg ######################################################################## 100.0% ==> No checksum defined for Cask google-chrome, skipping verification ==> Moving App 'Google Chrome.app' to '/Applications/Google Chrome.app'. 🍺 google-chrome was successfully installed! /Applications » chrome --version Google Chrome 58.0.3029.81 /Applications » chrome --headless [0420/114015.498386: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. zsh: segmentation fault /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --headless /Applications » What is the expected behavior? --headless should launch as it did for 57 stable. What went wrong? Segmentation fault when using the --headless flag. Did this work before? Yes 57.0.2987.133 Does this work in other browsers? Yes Chrome version: 58.0.3029.81 Channel: stable OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 25.0 r0
,
Apr 21 2017
,
Apr 24 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by phistuck@chromium.org
, Apr 20 2017Labels: -Hotlist-Interop Proj-Headless