Sync compositor: Ignore command buffer memory callback

content/browser/android/in_process/synchronous_compositor_context_provider.cc

Index: content/browser/android/in_process/synchronous_compositor_context_provider.cc
diff --git a/content/browser/android/in_process/synchronous_compositor_context_provider.cc b/content/browser/android/in_process/synchronous_compositor_context_provider.cc
new file mode 100644
index 0000000000000000000000000000000000000000..94040b2b07ef8d485230df20e7e98cd5a2d3e6f9
--- /dev/null
+++ b/content/browser/android/in_process/synchronous_compositor_context_provider.cc
@@ -0,0 +1,21 @@
+// Copyright (c) 2015 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "content/browser/android/in_process/synchronous_compositor_context_provider.h"
+
+namespace content {
+
+SynchronousCompositorContextProvider::SynchronousCompositorContextProvider(
+    scoped_ptr<WebGraphicsContext3DCommandBufferImpl> context3d,
+    CommandBufferContextType type)
+    : ContextProviderCommandBuffer(context3d.Pass(), type, false) {}
+
+SynchronousCompositorContextProvider::~SynchronousCompositorContextProvider() {}
+
+void SynchronousCompositorContextProvider::SetMemoryPolicyChangedCallback(
+    const MemoryPolicyChangedCallback& memory_policy_changed_callback) {
+  // Intentional no-op.

[no sievers, 2015/08/05 22:31:27]

But this can be NOTREACHED() then?

[boliu, 2015/08/05 22:35:04]

Nope.. it's still called. But this override is technically not really needed.
Setting the callback in provider doesn't hurt anything, as long as it's not
hooked up to the command buffer.

Ehh, I'll get rid of it.

+}
+
+}  // namespace content