cc: Set the mapped memory reclaim limit for the renderer compositor on Android

cc/trees/layer_tree_settings.cc

Index: cc/trees/layer_tree_settings.cc
diff --git a/cc/trees/layer_tree_settings.cc b/cc/trees/layer_tree_settings.cc
index 62fd261ef8251a054c282a84d25ce12460a571ff..6374a5208c9027d3f82a0326e9a5f631873050d9 100644
--- a/cc/trees/layer_tree_settings.cc
+++ b/cc/trees/layer_tree_settings.cc
@@ -57,7 +57,8 @@ LayerTreeSettings::LayerTreeSettings()
       strict_layer_property_change_checking(false),
       use_map_image(false),
       compositor_name("ChromiumCompositor"),
-      ignore_root_layer_flings(false) {
+      ignore_root_layer_flings(false),
+      max_transfer_buffer_usage_bytes(0) {

[danakj, 2013/08/23 01:21:46]

Is there a reason for this to default to 0 in prod?

[kaanb, 2013/08/23 01:37:31]

We only initialize it to 0, it's always being assigned later when we create the
compositor. We also have a DCHECK in PBRWP to guarantee that it is always
assigned a valid value.

[danakj, 2013/08/23 01:53:07]

I'm just wondering cuz if you initialize it to something big here then you don't
have to do anything anywhere for tests. If there's some worry about prod places
not init'ing it or something?

   // TODO(danakj): Renable surface caching when we can do it more realiably.
   // crbug.com/170713
   cache_render_pass_contents = false;