Headless Failed to launch GPU process.
Reported by
hemanth...@gmail.com,
May 2 2017
|
|||||
Issue descriptionOn chrome canary. $ alias chrome-canary="/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary" $ chrome-canary --headless [0501/215816.739888:ERROR:file_io_posix.cc(149)] open /Applications/Google Chrome Canary.app/Contents/Versions/60.0.3086.0/Google Chrome Framework.framework/Versions/A/settings.dat: Permission denied [0501/215816.740763:INFO:crashpad_client_mac.cc(295)] restarting handler in 0.991s [0501/215816.740793:ERROR:file_io_posix.cc(149)] open /Applications/Google Chrome Canary.app/Contents/Versions/60.0.3086.0/Google Chrome Framework.framework/Versions/A/settings.dat: Permission denied [0501/215816.852516:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process. $ sudo !! sudo chrome-canary --headless Password: [0501/215824.447718:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process. $ system_profiler SPDisplaysDataType | grep 'Chipset Model:' | cut -f2- -d':' | tr -d ' ' AMDRadeonR9M370X IntelIrisPro
,
May 5 2017
skyostil, could you please triage?
,
May 8 2017
You currently need to start the browser with --disable-gpu because we aren't able to use SwiftShader for headless yet.
,
May 15 2017
,
Jan 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sureshkumari@chromium.org
, May 2 2017Labels: TE-NeedsTriageHelp