New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 608533 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2016
Cc:
penghuang@chromium.org
█ markdittmer@chromium.org
rjkroege@chromium.org
vmi...@chromium.org
sadrul@chromium.org
piman@chromium.org
█ jbau...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
mus



Sign in to add a comment

Get rid of kSwitchNames in gpu_process_host.cc

Project Member Reported by fsam...@chromium.org, May 2 2016 
We now have two ways to propagate switches to the gpu service: command line switches and a GpuPreferences object.

I'm seeing people continue to update both kSwitchNames and GpuPreferences.

We should get rid of kSwitchNames to discourage this behavior, I think to avoid the potential of the two methods disagreeing with one another, and to avoid new usage of switches in the gpu service. WDYT, Antoine?

Comment 1 by fsam...@chromium.org, May 2 2016

Cc: jbau...@chromium.org

Comment 2 by piman@chromium.org, May 3 2016 

As discussed, there's a bunch of flags we likely can't move to GpuPreferences, or anything really because they're needed before we setup the channel (e.g. sandbox flags, tracing flags, logging flags, etc.).
In general I wouldn't want to add to GpuPreferences flags that don't have anything to do with gpu/.

Comment 3 by fsam...@chromium.org, May 3 2016

Status: WontFix (was: Untriaged)
Marking as wontfix.
►

Sign in to add a comment