Make lost context and error message callbacks on GpuControl go to client

components/mus/gles2/command_buffer_local.cc

Index: components/mus/gles2/command_buffer_local.cc
diff --git a/components/mus/gles2/command_buffer_local.cc b/components/mus/gles2/command_buffer_local.cc
index 23a8fd1e50fdae5a3e34160fa76ca384c2e2174e..20f0756ddf4eba0e607ca85e1b5c767d7faf24cb 100644
--- a/components/mus/gles2/command_buffer_local.cc
+++ b/components/mus/gles2/command_buffer_local.cc
@@ -216,6 +216,12 @@ void CommandBufferLocal::DestroyTransferBuffer(int32_t id) {
                  base::Unretained(this), id));
 }
 
+void CommandBufferLocal::SetGpuControlClient(gpu::GpuControlClient*) {
+  // This implementation of GpuControl has no concept of losing the context
+  // (see IsGpuChannelLost), and no error messages, so we don't bother storing
+  // the client.

[no sievers, 2016/04/07 21:07:58]

It does handle lost contexts and trigger the callback to the client though. It's
just that it's forwarded from CommandBufferDriver to
CommandBufferLocal::DidLoseContext() separately.

I guess this class is something like GLInProcessContext/InProcessCommandBuffer
which blurs the notion of client/service a bit.

[danakj, 2016/04/07 21:45:18]

Ooops thanks, I was looking for "Lost" not "Lose".

So the SurfacesContextProvider should just pass the lost context callback given
to it thru to the GLES2Impl, and this will call the GLES2Impl on loss.

Removing DidLoseContext from the CommandBufferLocalClient.

+}
+
 gpu::Capabilities CommandBufferLocal::GetCapabilities() {
   DCHECK(CalledOnValidThread());
   return capabilities_;