Introduce moderate binding

tools/metrics/actions/actions.xml

Index: tools/metrics/actions/actions.xml
diff --git a/tools/metrics/actions/actions.xml b/tools/metrics/actions/actions.xml
index 009f60669b51c42016bc9da7cbc7260264557fba..466182be1221f35b4d2bf5ef13ed83d19053fbc8 100644
--- a/tools/metrics/actions/actions.xml
+++ b/tools/metrics/actions/actions.xml
@@ -7512,6 +7512,14 @@ should be able to be added at any place in this file.
   <description>Please enter the description of this user action.</description>
 </action>
 
+<action name="MobileBackgroundRendererCrashedOnForegroundApp">

[Alexei Svitkine (slow), 2015/06/17 16:57:22]

What's the reason for making this an action rather than a boolean histogram?

[Jaekyun Seok (inactive), 2015/06/17 22:31:50]

We are already using an action named "MobileRendererCrashed" to log renderer
crash in the foreground;
https://cs.corp.google.com/#clankium/src/chrome/browser/android/metrics/uma_s....

So I introduced another action to log renderer crash in the background. Do you
think that using a histogram is properer?

[Alexei Svitkine (slow), 2015/06/18 15:34:33]

Yeah, in my opinion it would be better to combine the two actions into a single
enumerated histogram with two buckets.

Histograms are better supported by our dashboards (e.g. allow filters) and are
also more efficient.

+  <owner>jaekyun@chromium.org</owner>
+  <description>
+    A renderer process is crashed in the background while an application is in
+    the foreground.
+  </description>
+</action>
+
 <action name="MobileBeamCallbackSuccess">
   <owner>Please list the metric's owners. Add more owner tags as needed.</owner>
   <description>Please enter the description of this user action.</description>