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

content/common/gpu/gpu_command_buffer_stub.h

Index: content/common/gpu/gpu_command_buffer_stub.h
diff --git a/content/common/gpu/gpu_command_buffer_stub.h b/content/common/gpu/gpu_command_buffer_stub.h
index 4f0881843804ef595e2d5134e51ad731b03c34ea..712e817915ad202f0f0d8782d715764110ee0ccc 100644
--- a/content/common/gpu/gpu_command_buffer_stub.h
+++ b/content/common/gpu/gpu_command_buffer_stub.h
@@ -146,6 +146,8 @@ class GpuCommandBufferStub
     return (surface_state_.get()) ? surface_state_->surface_id : 0;
   }
 
+  bool is_ui_stub() const { return handle_.handle; }

[mmocny, 2012/04/18 20:43:11]

This was a quick solution to a problem.  It warrents a discussion, and I'll post
comments soon.

[piman, 2012/04/18 22:20:14]

nak... this is not true on non-aura (FTM even on aura if --ui-use-gpu-process
isn't set).
Besides, the GPU side shouldn't have to know anything about the UI.

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

Yes, ideally incoming allocation hints are sufficient to prioritize allocations.
 Since we don't have those yet, I was hoping to ignore the UI, but that does
seem to be trouble.
On 2012/04/18 22:20:14, piman wrote:

+
   // Identifies the various GpuCommandBufferStubs in the GPU process belonging
   // to the same renderer process.
   int32 route_id() const { return route_id_; }