Performance monitor stats gathering.

base/process_util_win.cc

Index: base/process_util_win.cc
diff --git a/base/process_util_win.cc b/base/process_util_win.cc
index 55d2959c10813a6297e5b9e73418eb85e6d42389..c0a1e37b229ef4ff2a25bd7c9074c42b5ec178b5 100644
--- a/base/process_util_win.cc
+++ b/base/process_util_win.cc
@@ -731,8 +731,10 @@ bool ProcessMetrics::GetMemoryBytes(size_t* private_bytes,
 
   if (shared_bytes) {
     WorkingSetKBytes ws_usage;
-    if (!GetWorkingSetKBytes(&ws_usage))
+    if (!GetWorkingSetKBytes(&ws_usage)) {
+      LOG(ERROR) << "GetMemoryBytes return false";

[Devlin, 2012/07/24 15:30:48]

Debug statements generally don't go in CL's.

[mitchellwrosen, 2012/07/27 19:24:51]

I know. It was an accident =P

       return false;
+    }
 
     *shared_bytes = ws_usage.shared * 1024;
   }
@@ -798,6 +800,7 @@ bool ProcessMetrics::GetWorkingSetKBytes(WorkingSetKBytes* ws_usage) const {
             realloc(buffer, buffer_size));
     if (!new_buffer) {
       free(buffer);
+      LOG(ERROR) << "GetWorkingSetKBytes returning false 1";
       return false;
     }
     buffer = new_buffer;
@@ -808,6 +811,8 @@ bool ProcessMetrics::GetWorkingSetKBytes(WorkingSetKBytes* ws_usage) const {
 
     if (GetLastError() != ERROR_BAD_LENGTH) {
       free(buffer);
+      LOG(ERROR) << "GetWorkingSetKBytes: GetLastError() == " << GetLastError();
+      LOG(ERROR) << "GetWorkingSetKBytes returning false 2";
       return false;
     }
 
@@ -819,6 +824,7 @@ bool ProcessMetrics::GetWorkingSetKBytes(WorkingSetKBytes* ws_usage) const {
 
     if (--retries == 0) {
       free(buffer);  // If we're looping, eventually fail.
+      LOG(ERROR) << "GetWorkingSetKBytes returning false 3";
       return false;
     }
   }