OOR-CORS: Change metric range for PreflightCacheTotalMemoryPressureInBytes

UMA_HISTOGRAM_COUNTS_10000 was to small for measuring total memory
pressure in bytes. 10M or larger range would be preferable.

Bug: 961602
Change-Id: I4e94ca973d65a74860cd16a0d424e1ea128a39b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1619452
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#661312}
diff --git a/services/network/network_service.cc b/services/network/network_service.cc
index 66a4e20..a3fd130 100644
--- a/services/network/network_service.cc
+++ b/services/network/network_service.cc
@@ -830,9 +830,8 @@
     loader_count += context->GatherActiveLoaderCount();
   }
   UMA_HISTOGRAM_COUNTS_10000("Net.Cors.PreflightCacheTotalEntries", cache_size);
-  UMA_HISTOGRAM_COUNTS_10000(
-      "Net.Cors.PreflightCacheTotalMemoryPressureInBytes",
-      memory_pressure_in_bytes);
+  UMA_HISTOGRAM_COUNTS_10M("Net.Cors.PreflightCacheTotalMemoryPressureInBytes",
+                           memory_pressure_in_bytes);
   UMA_HISTOGRAM_COUNTS_1000("Net.Cors.ActiveLoaderCount", loader_count);
 }