PyAuto test for GPU memory consumption

content/common/gpu/gpu_memory_manager.h

Index: content/common/gpu/gpu_memory_manager.h
diff --git a/content/common/gpu/gpu_memory_manager.h b/content/common/gpu/gpu_memory_manager.h
index e51559dd472b8696fbcd200ae81625d9471e9e57..ea9437c53a40be52c71c56ac64863018fa14b7bb 100644
--- a/content/common/gpu/gpu_memory_manager.h
+++ b/content/common/gpu/gpu_memory_manager.h
@@ -14,6 +14,7 @@
 #include "base/cancelable_callback.h"
 #include "base/memory/weak_ptr.h"
 #include "content/common/content_export.h"
+#include "content/public/common/gpu_mem_stats.h"
 
 class GpuCommandBufferStubBase;
 
@@ -58,6 +59,9 @@ class CONTENT_EXPORT GpuMemoryManager :
   // queued delayed manage.
   void ScheduleManage(bool immediate);
 
+  // Populate stats with statistics on memory usage
+  void GetMemStats(content::GpuMemStats& stats);

[mmocny, 2012/07/17 19:26:04]

In the CL I posted, I proposed GpuMemoryManager providing stats using data
structures that make the most sense for it, not for particular tests.

Since there may be a suite of tests for various purposes, I think it may be
better for content::GpuMemStats (which is really GpuMemStatsNeededForTestX) to
be filled in outside of GpuMemoryManager.

[ccameron, 2012/07/17 20:00:47]

Yeah, I thought this would be the case -- I'll update the patch to put the logic
outside of GpuMemoryManager (I originally included this just to make sure that
calling in did indeed work).

+
  private:
   friend class GpuMemoryManagerTest;
   void Manage();