Apply gpu workarounds.

services/gles2/gpu_state.cc

Index: services/gles2/gpu_state.cc
diff --git a/services/gles2/gpu_state.cc b/services/gles2/gpu_state.cc
index 911477114cea8a9dc0b48a6fb7a654ccf5c386f8..04ddf0f70eddf3ac674e28f65b978b6209458a49 100644
--- a/services/gles2/gpu_state.cc
+++ b/services/gles2/gpu_state.cc
@@ -5,6 +5,8 @@
 
 #include "services/gles2/gpu_state.h"
 
+#include "base/command_line.h"
+#include "gpu/config/gpu_util.h"
 #include "services/gles2/mailbox_manager_factory.h"
 
 namespace gles2 {
@@ -14,6 +16,8 @@ GpuState::GpuState()
       sync_point_manager_(gpu::SyncPointManager::Create(true)),
       share_group_(new gfx::GLShareGroup),
       mailbox_manager_(MailboxManagerFactory::Create()) {
+  gpu::ApplyGpuDriverBugWorkarounds(base::CommandLine::ForCurrentProcess());

[jamesr, 2015/09/18 16:34:09]

what populates the workaround list? the way this works in chrome is the browser
proc generates a bunch of stuff into the command line for the gpu process when
then gets populated here. maybe the command line parameter isn't actually used?

[cdotstout, 2015/09/18 17:54:04]

Some workarounds are set automatically based on the gpu, a good example being
the adreno 420 fix for framebuffer deletion.

The commandline provides additional workarounds (see
GpuDriverBugList::AppendWorkaroundsFromCommandLine).  In this case, the
commandline happens to be empty.  I'm not sure we want to actually use a command
line for this, maybe it would be better to just construct an empty command line
and pass that in.

+
   control_thread_.Start();
 }