summaryrefslogtreecommitdiffstats
path: root/content/browser/browser_child_process_host.cc
diff options
context:
space:
mode:
authorpetkov@chromium.org <petkov@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-10-19 22:06:18 +0000
committerpetkov@chromium.org <petkov@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-10-19 22:06:18 +0000
commit80bb87e812e8bf4890f5e485ae69a506ea0b2a21 (patch)
treeb070ba7716413cf3c701ec9a402775b834907e1d /content/browser/browser_child_process_host.cc
parentafbfa25e3240333fd5355448c2c8e94b1e3103bf (diff)
downloadchromium_src-80bb87e812e8bf4890f5e485ae69a506ea0b2a21.zip
chromium_src-80bb87e812e8bf4890f5e485ae69a506ea0b2a21.tar.gz
chromium_src-80bb87e812e8bf4890f5e485ae69a506ea0b2a21.tar.bz2
Count all abnormal child process exits in a ChildProcess.Disconnected histogram.
For now, this should give us a good way to monitor PPAPI crashes on Chrome OS in the field. In addition, it also shows all abnormal disconnects that are not counted in the other ChildProcess.* histograms. BUG=chromium-os:21753 TEST=kill -SEGV PPAPI process, inspect about:histogram Change-Id: I67320008ce44f5a86448fe648841993ddeb96cf8 Review URL: http://codereview.chromium.org/8329014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@106396 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/browser_child_process_host.cc')
-rw-r--r--content/browser/browser_child_process_host.cc2
1 files changed, 2 insertions, 0 deletions
diff --git a/content/browser/browser_child_process_host.cc b/content/browser/browser_child_process_host.cc
index 50271cc..e2e99a5 100644
--- a/content/browser/browser_child_process_host.cc
+++ b/content/browser/browser_child_process_host.cc
@@ -179,6 +179,8 @@ void BrowserChildProcessHost::OnChildDisconnected() {
default:
break;
}
+ UMA_HISTOGRAM_ENUMERATION("ChildProcess.Disconnected",
+ this->type(), MAX_PROCESS);
// Notify in the main loop of the disconnection.
Notify(content::NOTIFICATION_CHILD_PROCESS_HOST_DISCONNECTED);
OnChildDied();