Move SharedMemoryLimits out of WebGraphicsContext3DCommandBufferImpl.

blimp/client/feature/compositor/blimp_context_provider.cc

Index: blimp/client/feature/compositor/blimp_context_provider.cc
diff --git a/blimp/client/feature/compositor/blimp_context_provider.cc b/blimp/client/feature/compositor/blimp_context_provider.cc
index a1ee746843246c752910750896c206cb9b21b992..4d0e06e5445f08a2aa8616e557808d93f7848f71 100644
--- a/blimp/client/feature/compositor/blimp_context_provider.cc
+++ b/blimp/client/feature/compositor/blimp_context_provider.cc
@@ -56,8 +56,6 @@ BlimpContextProvider::~BlimpContextProvider() {
 
 bool BlimpContextProvider::BindToCurrentThread() {
   DCHECK(context_thread_checker_.CalledOnValidThread());
-  capabilities_.gpu = context_->GetImplementation()->capabilities();
-  capabilities_.gpu.image = true;
   return true;
 }
 
@@ -65,9 +63,14 @@ void BlimpContextProvider::DetachFromThread() {
   context_thread_checker_.DetachFromThread();
 }
 
-cc::ContextProvider::Capabilities BlimpContextProvider::ContextCapabilities() {
+gpu::Capabilities BlimpContextProvider::ContextCapabilities() {
   DCHECK(context_thread_checker_.CalledOnValidThread());
-  return capabilities_;
+  gpu::Capabilities capabilities =
+      context_->GetImplementation()->capabilities();
+  // TODO(danakj): Why? Is this even valid? This is the CHROMIUM_image extension

[danakj, 2016/04/19 02:02:11]

I can try investigate this

[piman, 2016/04/19 03:22:17]

It should already be set to true if the GpuMemoryBufferManager is not null (see
InProcessCommandBuffer::Initialize)
If the GMBManger is null, you don't want to use CHROMIUM_image

So yeah, this is suspicious.

[no sievers, 2016/04/19 20:24:13]

I'm guessing this is either a copy&paste from somewhere or made some DHCECK() go
away or so. And nobody expected this to be actually working yet, see
crbug.com/577265. I'd just try to remove it.

However at this point I'm not sure what Blimp is doing with GLInProcessContext
anyways.

[danakj, 2016/04/20 00:01:53]

This is in https://codereview.chromium.org/1898983003/ to remove.

+  // to use GpuMemoryBuffers. Does the context not provide this?
+  capabilities.image = true;
+  return capabilities;
 }
 
 gpu::gles2::GLES2Interface* BlimpContextProvider::ContextGL() {