New issue
Advanced search Search tips
Starred by 8 users

Issue metadata

Status: Assigned
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocked on:
issue 729961

Sign in to add a comment

Headless: make --disable-gpu flag unnecessary

Project Member Reported by, Jun 28 2017 Back to list

Issue description

In the various documentation/guides for headless, the --disable-gpu flag is recommended. 

My understanding is that it's required because " is not there"
I've seen a few related errors printed, e.g.

> Failed to launch GPU process. 
> [] Failed to load /opt/google/chrome/ /opt/google/chrome/ cannot open shared object file: No such file or directory
[] Exiting GPU process due to errors during initialization

--disable-gpu does seem to be successful in addressing these problems right now.


I have a few questions:

1. Is this flag currently required on all platforms, or just Linux? 
2. Is it *always* required on Linux, or it depends on the host machine?
3. Can we make it unnecessary? Basically, if we're in --headless and no libobmesa is found, then we proceed as if --disable-gpu is set?
Blockedon: 729961
This flag is no longer necessary on Linux or macOS. It will become unnecessary on Windows as soon as bug 729961 is fixed.
Ah sweet.
Can you help me find what crrev this was made unnecessary on Linux and Mac? AFAIK it's needed on stable, just want to update documentation. :) 
Any updates on this for Windows?
Nope, sorry, still on my backlog.

Sign in to add a comment