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

content/common/gpu/gpu_messages.h

Index: content/common/gpu/gpu_messages.h
diff --git a/content/common/gpu/gpu_messages.h b/content/common/gpu/gpu_messages.h
index d76491aa20e8179d37fd66e494bba6ba34026599..e33e0938127ec0b46802e14f81ef716e28ac462d 100644
--- a/content/common/gpu/gpu_messages.h
+++ b/content/common/gpu/gpu_messages.h
@@ -445,6 +445,9 @@ IPC_MESSAGE_ROUTED0(GpuCommandBufferMsg_EnsureBackbuffer)
 IPC_MESSAGE_ROUTED1(GpuCommandBufferMsg_SetMemoryAllocation,
                     GpuMemoryAllocationForRenderer /* allocation */)
 
+// Sent to stub when proxy is assigned a memory allocation changed callback.
+IPC_MESSAGE_ROUTED0(GpuCommandBufferMsg_HandlesMemoryAllocations)

[nduca, 2012/04/23 22:12:18]

Not loving this. Also, how do you set it back to zero? See my overall notes
about making this a longer name that is closely tied to the callback.

Perhaps SetClientHasMemoryAllocationChangedCallback(bool)

+
 //------------------------------------------------------------------------------
 // Accelerated Video Decoder Messages
 // These messages are sent from Renderer process to GPU process.