Native memory histograms for the browser.

content/common/child_process_messages.h

Index: content/common/child_process_messages.h
diff --git a/content/common/child_process_messages.h b/content/common/child_process_messages.h
index 0cf2a3a69499358e9413cc40b62b3a0cac47a0fe..286c2d9f97ff566b2c95f1f1984fcaf24febedfd 100644
--- a/content/common/child_process_messages.h
+++ b/content/common/child_process_messages.h
@@ -108,6 +108,13 @@ IPC_MESSAGE_CONTROL2(ChildProcessHostMsg_ChildHistogramData,
                      int, /* sequence_number */
                      std::vector<std::string> /* histogram_data */)
 
+// Request a histogram from the browser. The browser will send the histogram
+// data only if it has been passed the command line flag
+// switches::kMemoryMetrics.
+IPC_SYNC_MESSAGE_CONTROL1_1(ChildProcessHostMsg_GetBrowserHistogram,

[nduca, 2013/01/31 04:20:11]

is there any security risk here with a compromised render process? Effectivley,
all local histograms are exposed via this ipc.

[marja, 2013/01/31 08:19:36]

The browser only replies with data if it was passed a specific command line
flag, and if the histogram is one of the whitelisted histograms.

+                            std::string, /* histogram_name */
+                            std::string /* histogram_json */)
+
 // Reply to ChildProcessMsg_DumpHandles when handle table dump is complete.
 IPC_MESSAGE_CONTROL0(ChildProcessHostMsg_DumpHandlesDone)