Send memory management policies to the tile manager

cc/thread_proxy.cc

Index: cc/thread_proxy.cc
diff --git a/cc/thread_proxy.cc b/cc/thread_proxy.cc
index b7e0e7c405e9c5518d600b6b875f37ab72fbabca..d67c434174d5118655a5a8c124bfcb11ed777ed8 100644
--- a/cc/thread_proxy.cc
+++ b/cc/thread_proxy.cc
@@ -397,6 +397,11 @@ void ThreadProxy::sendManagedMemoryStats()
     if (!m_layerTreeHost->contentsTextureManager())
         return;
 
+    // If we are using impl-side painting, then sendManagedMemoryStats is called
+    // through the tile manager's manage function.
+    if (m_layerTreeHostImpl->tileManager())

[nduca, 2012/12/28 02:16:03]

Shoud we use settings.implSidePainting? I dont have a strong opinion...

[ccameron, 2012/12/28 19:56:00]

Yes, that's the right signal.

+        return;
+
     m_layerTreeHostImpl->sendManagedMemoryStats(
         m_layerTreeHost->contentsTextureManager()->memoryVisibleBytes(),
         m_layerTreeHost->contentsTextureManager()->memoryVisibleAndNearbyBytes(),