Add onMemoryDump to GrContext

include/gpu/GrContext.h

Index: include/gpu/GrContext.h
diff --git a/include/gpu/GrContext.h b/include/gpu/GrContext.h
index cb5eb761ed97545de92c79581b66863dcc23184a..c4bdcbd8b27c34137ecc97d5f127e22987dec75c 100644
--- a/include/gpu/GrContext.h
+++ b/include/gpu/GrContext.h
@@ -43,6 +43,7 @@ class GrTextureParams;
 class GrVertexBuffer;
 class GrStrokeInfo;
 class GrSoftwarePathRenderer;
+class SkTraceMemoryDump;
 
 class SK_API GrContext : public SkRefCnt {
 public:
@@ -361,6 +362,9 @@ public:
         to an array of 3 entries */
     void setTextContextAtlasSizes_ForTesting(const GrBatchAtlasConfig* configs);
 
+    /** Enumerates all cached GPU resources and dumps their memory to traceMemoryDump. */
+    void onMemoryDump(SkTraceMemoryDump* traceMemoryDump) const;

[bsalomon, 2015/08/26 16:36:00]

Can we call this something like dumpMemory? We usually use "on" for private
virtual methods that implement non virtual public methods.

[ericrk, 2015/08/26 17:01:09]

OnMemoryDump matches the name in chrome, but I'm happy with whatever you think
makes most sense for Skia. In the SW dumping code, we currently have
DumpMemoryStatistics, but that isn't checked in yet (CL here:
https://codereview.chromium.org/1319473003)

I'll switch to DumpMemoryStatistics to match our planned SW name - does that
work for you?

[bsalomon, 2015/08/26 17:08:56]

sgtm

+
 private:
     GrGpu*                          fGpu;
     const GrCaps*                   fCaps;