This adds some plumbing for propagating the reason for a renderer's death

chrome/browser/metrics/metrics_service.cc

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 
 
 //------------------------------------------------------------------------------
 // Description of the life cycle of a instance of MetricsService.
 //
 //  OVERVIEW
@@ skipping 588 matching lines @@
       break;
 
     case NotificationType::LOAD_STOP:
       LogLoadComplete(type, source, details);
       break;
 
     case NotificationType::LOAD_START:
       LogLoadStarted();
       break;
 
-    case NotificationType::RENDERER_PROCESS_CLOSED:
-      {
+    case NotificationType::RENDERER_PROCESS_CLOSED: {
         RenderProcessHost::RendererClosedDetails* process_details =
             Details<RenderProcessHost::RendererClosedDetails>(details).ptr();
-        if (process_details->did_crash) {
+        if (process_details->status ==
+            base::TERMINATION_STATUS_PROCESS_CRASHED ||
+            process_details->status ==
+            base::TERMINATION_STATUS_ABNORMAL_TERMINATION) {

[Greg Spencer (Chromium), 2010/12/03 01:00:07]

I'm wondering if I should be adding logging here for renderer/extension "kills".
 We didn't report those previously because we didn't trap them.

           if (process_details->was_extension_renderer) {
             LogExtensionRendererCrash();
           } else {
             LogRendererCrash();
           }
         }
       }
       break;
 
     case NotificationType::RENDERER_PROCESS_HANG:
@@ skipping 1282 matching lines @@
     thread_id = PlatformThread::CurrentId();
   return PlatformThread::CurrentId() == thread_id;
 }
 
 #if defined(OS_CHROMEOS)
 void MetricsService::StartExternalMetrics() {
   external_metrics_ = new chromeos::ExternalMetrics;
   external_metrics_->Start();
 }
 #endif