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 784843737e613e7d0e3bb02a7790819a225811fb..1ec70a7541779152b037a10f1f57fbfa4f4eed9d 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -11438,6 +11438,13 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   </summary>
 </histogram>
 
+<histogram name="GPU.ContextLost" enum="ContextLostReason">
+  <owner>sievers@chromium.org</owner>
+  <summary>
+    The reason a GPU command buffer context of a given type was lost.
+  </summary>
+</histogram>
+
 <histogram name="GPU.CreateBrowserCompositor" units="microseconds">
   <owner>vangelis@chromium.org</owner>
   <summary>
@@ -48073,6 +48080,22 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="22" label="App banner setting (Android only)"/>
 </enum>
 
+<enum name="ContextLostReason" type="int">
+  <summary>The reason for losing a GPU context.</summary>
+  <int value="0" label="CONTEXT_INIT_FAILED"/>
+  <int value="1" label="CONTEXT_LOST_GPU_CHANNEL_ERROR"/>
+  <int value="2" label="CONTEXT_PARSE_ERROR_INVALID_SIZE"/>
+  <int value="3" label="CONTEXT_PARSE_ERROR_OUT_OF_BOUNDS"/>
+  <int value="4" label="CONTEXT_PARSE_ERROR_UNKNOWN_COMMAND"/>
+  <int value="5" label="CONTEXT_PARSE_ERROR_INVALID_ARGS"/>
+  <int value="6" label="CONTEXT_PARSE_ERROR_GENERIC_ERROR"/>
+  <int value="7" label="CONTEXT_LOST_GUILTY"/>
+  <int value="8" label="CONTEXT_LOST_INNOCENT"/>
+  <int value="9" label="CONTEXT_LOST_UNKNOWN"/>
+  <int value="10" label="CONTEXT_LOST_OUT_OF_MEMORY"/>
+  <int value="11" label="CONTEXT_LOST_MAKECURRENT_FAILED"/>
+</enum>
+
 <enum name="CookieDeletionCause" type="int">
   <summary>Reason why a cookie was removed from the cookie store</summary>
   <int value="0" label="explicit">
@@ -64686,6 +64709,26 @@ To add a new entry, add it with any value and run test to compute valid value.
   <affected-histogram name="PLT.LoadType"/>
 </histogram_suffixes>
 
+<histogram_suffixes name="ContextType">

[Alexei Svitkine (slow), 2015/04/24 20:01:31]

I think you need to add separator="." here.

[no sievers, 2015/04/24 20:12:50]

Done. It seems to default to "." though, because I was looking at
about:histograms where it looked as expected.

[Alexei Svitkine (slow), 2015/04/24 20:18:10]

about:histograms shows what the code logs, not what histograms.xml contains.

+  <suffix name="BrowserCompositor"
+      label="A BrowserCompositor GPU command buffer context"/>
+  <suffix name="BrowserMainThread"
+      label="A BrowserMainThread GPU command buffer context"/>
+  <suffix name="RenderCompositor"
+      label="A RenderCompositor GPU command buffer context"/>
+  <suffix name="RenderMainThread"
+      label="A RenderMainThread GPU command buffer context"/>
+  <suffix name="RenderWorker"
+      label="A RenderWorker GPU command buffer context"/>
+  <suffix name="Unknown" label="A GPU command buffer context of unknown type"/>
+  <suffix name="VideoAccelerator"
+      label="A VideoAccelerator GPU command buffer context"/>
+  <suffix name="VideoCapture"
+      label="A VideoCapture GPU command buffer context"/>
+  <suffix name="WebGL" label="A WebGL GPU command buffer context"/>
+  <affected-histogram name="GPU.ContextLost"/>
+</histogram_suffixes>
+
 <histogram_suffixes name="CreditCardScanSuccess">
   <suffix name="Completed" label="Credit card scan completed."/>
   <suffix name="Cancelled" label="Credit card scan was cancelled."/>