New issue
Advanced search Search tips

Issue 869466 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Headless broken in 69.0.3497.12 dev channel

Reported by dvpdin...@gmail.com, Jul 31

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.12 Safari/537.36

Steps to reproduce the problem:
$ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --headless --remote-debugging-port=9222 --disable-gpu https://dpogue.ca

What is the expected behavior?
The page loads in a headless browser and can be debugged from the chrome://inspect page in another instance.

What went wrong?
The headless browser does not open the page in question, several errors are printed in the terminal:

[0731/103741.180988:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.

DevTools listening on ws://127.0.0.1:9222/devtools/browser/efd6be50-aea1-404f-bef7-557a8255f8d5
[0731/103741.264546:ERROR:gl_implementation.cc(291)] Failed to load /Applications/Google Chrome.app/Contents/Versions/69.0.3497.12/Google Chrome Framework.framework/Versions/Current/Libraries/libswiftshader_libGLESv2.dylib: dlopen(/Applications/Google Chrome.app/Contents/Versions/69.0.3497.12/Google Chrome Framework.framework/Versions/Current/Libraries/libswiftshader_libGLESv2.dylib, 1): image not found
[0731/103741.444959:ERROR:gl_implementation.cc(291)] Failed to load /Applications/Google Chrome.app/Contents/Versions/69.0.3497.12/Google Chrome Framework.framework/Versions/Current/Libraries/libswiftshader_libGLESv2.dylib: dlopen(/Applications/Google Chrome.app/Contents/Versions/69.0.3497.12/Google Chrome Framework.framework/Versions/Current/Libraries/libswiftshader_libGLESv2.dylib, 1): no suitable image found.  Did find:
	/Applications/Google Chrome.app/Contents/Versions/69.0.3497.12/Google Chrome Framework.framework/Versions/Current/Libraries/libswiftshader_libGLESv2.dylib: file system sandbox blocked stat()
[0731/103741.474320:ERROR:viz_main_impl.cc(235)] Exiting GPU process due to errors during initialization

Did this work before? Yes Previous dev channel release of M69

Chrome version: 69.0.3497.12  Channel: dev
OS Version: OS X 10.13.6
Flash Version: 

It doesn't work regardless of whether the --disable-gpu flag is passed or not, but it only prints out the errors about libswiftshader when running with --disable-gpu.
 
This may already be fixed, because it appears to work in the Canary channel, but it still prints out the same errors about libswiftshader
Labels: Needs-Triage-M69 Needs-Bisect
Cc: phanindra.mandapaka@chromium.org
Components: -Platform>DevTools Internals>Headless
Labels: Triaged-ET
Labels: -Needs-Bisect
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 69.0.3497.12 & previous Dev 69.0.3493.3, latest chrome 70.0.3509.0 using Mac 10.13.5. 
 
From M-60 to M-62 able to see the chrome in task bar but not launching chrome browser and on M-63 observed inconsistent behavior hence considering it as non-regression and marking it as Untriaged.

NOTE: on Windows and Ubuntu tried to launch using given path observed that command is not executed and removing Needs-Bisect Label .

Thanks! 

Sign in to add a comment