Fix low-memory devices crashing on Chrome start up during UMA recodring

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 d35b748440551e69e2aa33f4ce0314fe28d72170..4da43ac3a907873c614ed0ed745605e01e551d77 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -2707,8 +2707,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <summary>Is low memory device.</summary>
 </histogram>
 
-<histogram name="ChromiumAndroidLinker.LibraryLoadFromApkSupported"
-    enum="BooleanSupported">
+<histogram name="ChromiumAndroidLinker.LibraryLoadFromApkStatus"
+    enum="LibraryLoadFromApkStatus">
   <owner>petrcermak@chromium.org</owner>
   <summary>
     Whether the device supports loading a library directly from the APK file.
@@ -40044,11 +40044,6 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="1" label="Success"/>
 </enum>
 
-<enum name="BooleanSupported" type="int">
-  <int value="0" label="Not supported"/>
-  <int value="1" label="Supported"/>
-</enum>
-
 <enum name="BooleanSuppressed" type="int">
   <int value="0" label="No suppressions"/>
   <int value="1" label="Suppressed"/>
@@ -46274,6 +46269,13 @@ Therefore, the affected-histogram name has to have at least one dot in it.
   <int value="256" label="FILE_NOT_SPECIFIED"/>
 </enum>
 
+<enum name="LibraryLoadFromApkStatus" type="int">
+  <int value="0" label="Unknown"/>
+  <int value="1" label="Not supported"/>
+  <int value="2" label="Supported"/>
+  <int value="3" label="Successful"/>
+</enum>
+
 <enum name="LinkMonitorFailureType" type="int">
   <int value="0" label="Local MAC Address Not Found"/>
   <int value="1" label="Client Startup Failure"/>