[tracing] Add graphics memory dump provider for Android

content/browser/browser_main_loop.cc

Index: content/browser/browser_main_loop.cc
diff --git a/content/browser/browser_main_loop.cc b/content/browser/browser_main_loop.cc
index 8a9a37de8ab6eec4c2bd228c0283ea38fdf180c8..305eff68211e4c264c6793042af339cb128501f0 100644
--- a/content/browser/browser_main_loop.cc
+++ b/content/browser/browser_main_loop.cc
@@ -87,6 +87,7 @@
 
 #if defined(OS_ANDROID)
 #include "base/android/jni_android.h"
+#include "components/tracing/graphics_memory_dump_provider_android.h"
 #include "content/browser/android/browser_startup_controller.h"
 #include "content/browser/android/browser_surface_texture_manager.h"
 #include "content/browser/android/in_process_surface_texture_manager.h"
@@ -1141,7 +1142,6 @@ int BrowserMainLoop::BrowserThreadsStarted() {
 
 #if !defined(OS_IOS)
   HistogramSynchronizer::GetInstance();
-
 #if defined(OS_ANDROID)
   // Up the priority of the UI thread.
   base::PlatformThread::SetCurrentThreadPriority(base::ThreadPriority::DISPLAY);
@@ -1173,6 +1173,10 @@ int BrowserMainLoop::BrowserThreadsStarted() {
   // BrowserProcessSubThread::IOThreadPreCleanUp).
   base::trace_event::MemoryDumpManager::GetInstance()->RegisterDumpProvider(
       BrowserGpuMemoryBufferManager::current(), io_thread_->task_runner());
+#if defined(OS_ANDROID)
+  base::trace_event::MemoryDumpManager::GetInstance()->RegisterDumpProvider(

[ericrk, 2015/10/02 18:30:11]

Do we need to register this in both Browser and GPU processes to handle the
in-proc GPU case? why is this needed at all in the browser proc?

[Primiano Tucci (use gerrit), 2015/10/05 14:24:25]

In the standard (non-in-proc) case I see that both browser and gpu process
provide data to meminfo. Are you suggesting that we only need one dumper at max,
in the process that hosts the gpu process?

[ericrk, 2015/10/05 20:32:21]

That's what I was thinking, but now that I think of it, we may need something in
the browser proc to catch allocations the Android system makes on our behalf?
Not 100% sure - I don't think this can hurt much, so please don't let this hold
up the CL. I'd like to see how these two numbers differ once we get this in.

+      tracing::GraphicsMemoryDumpProvider::GetInstance());
+#endif
 
   {
     TRACE_EVENT0("startup", "BrowserThreadsStarted::Subsystem:AudioMan");