cros: Log per-process memory use on low memory events

chrome/browser/automation/automation_provider_observers.cc

Index: chrome/browser/automation/automation_provider_observers.cc
diff --git a/chrome/browser/automation/automation_provider_observers.cc b/chrome/browser/automation/automation_provider_observers.cc
index b49a726257fab96218aea318b5e7554409f45644..b585f4638489e8be3e234c3624d1eaeada30a804 100644
--- a/chrome/browser/automation/automation_provider_observers.cc
+++ b/chrome/browser/automation/automation_provider_observers.cc
@@ -2718,6 +2718,10 @@ ProcessInfoObserver::ProcessInfoObserver(
 ProcessInfoObserver::~ProcessInfoObserver() {}
 
 void ProcessInfoObserver::OnDetailsAvailable() {
+  // TODO(jamescook): Remove this.  I don't think we want it for automated
+  // tests, but it's how the system has always worked.

[Greg Spencer (Chromium), 2012/04/20 00:28:21]

Can you elaborate on what "this" and "it's" refer to here? (I mean, I know
"this" refers to the function call, but what does the function call imply?)
Otherwise I'm unclear why you added it if you put in a TODO to remove it.

+  UpdateHistograms();
+
   scoped_ptr<DictionaryValue> return_value(new DictionaryValue);
   ListValue* browser_proc_list = new ListValue();
   const std::vector<ProcessData>& all_processes = processes();