Kill renderers for bad password forms in --site-per-process.

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index ea110b9d7b4be2b0f7cfa6091f0e96200de9f0d0..12664ffd6b87d4717611de26be0d638317f3c928 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -41912,6 +41912,16 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   </summary>
 </histogram>
 
+<histogram name="Stability.BadMessageTerminated.PasswordManager"
+    enum="BadMessageReasonPasswordManager">
+  <owner>nick@chromium.org</owner>
+  <owner>jamescook@chromium.org</owner>
+  <summary>
+    Count of processes killed because they sent a bad IPC that couldn't be
+    properly handled. Categories are the reasons (code locations) for the kills.
+  </summary>
+</histogram>
+
 <histogram name="Stability.BrowserExitCodes" enum="WindowsExitCode">
   <owner>siggi@chromium.org</owner>
   <owner>erikwright@chromium.org</owner>
@@ -50478,6 +50488,12 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
   <int value="2" label="NHMF_GET_NEXE_FD_BAD_URL"/>
 </enum>
 
+<enum name="BadMessageReasonPasswordManager" type="int">
+<!-- Generated from components/password_manager/content/browser/bad_message.h -->
+
+  <int value="0" label="CPMD_BAD_ORIGIN"/>
+</enum>
+
 <enum name="BadSyncDataReason" type="int">
   <int value="0" label="Bad extension ID"/>
   <int value="1" label="Bad version"/>