GpuMemoryManager suggests values for renderer Contents Texture Managers' preferred memory limit.

content/common/gpu/gpu_channel.cc

Index: content/common/gpu/gpu_channel.cc
diff --git a/content/common/gpu/gpu_channel.cc b/content/common/gpu/gpu_channel.cc
index 96c3553010c5a84133af5f625ad8c03200a06799..2ef95a71725fd0bff33160553d684b85f999d290 100644
--- a/content/common/gpu/gpu_channel.cc
+++ b/content/common/gpu/gpu_channel.cc
@@ -128,7 +128,10 @@ void GpuChannel::AppendAllCommandBufferStubs(
     std::vector<GpuCommandBufferStubBase*>& stubs) {
   for (StubMap::Iterator<GpuCommandBufferStub> it(&stubs_);
       !it.IsAtEnd(); it.Advance()) {
-    stubs.push_back(it.GetCurrentValue());
+    GpuCommandBufferStub* stub = it.GetCurrentValue();

[nduca, 2012/04/18 23:16:28]

Is the idea here that we shouldnt give management callbacks to aura?

[mmocny, 2012/04/20 18:37:55]

Yes, until we get allocation hints I didn't want to give aura a large share of
the artificial limit.
Maybe this is not necessary but at the moment if you have only 1 window open,
aura has 2 stubs and a 3rd for popups etc so the wk renderer gets only 1/4 of
the global limit.
Maybe this is the wrong direction, but I wanted to prioritize wk compositor.
On 2012/04/18 23:16:28, nduca wrote:

+    if (stub->is_ui_stub())
+      continue;
+    stubs.push_back(stub);
   }
 }