Avoid allocation in OnOOMCallback

This CL tries to solve crashes in OnOOMCallback, which seem to happen because of allocation inside the function. By initializing the CrashMemoryReporterImpl in blink initializer, this fix intends to avoid allocation when memory pressure is high.


Bug: 888970
Change-Id: Iefc72224f95158e72030862c9d4cad8f964a4e1e
Reviewed-on: https://chromium-review.googlesource.com/c/1275745Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598711}

third_party/blink/renderer/controller/blink_initializer.cc

@@ -134,6 +134,12 @@ void InitializeCommon(Platform* platform,
     if (task_runner)
       MemoryAblationExperiment::MaybeStartForRenderer(task_runner);
   }
+
+#if defined(OS_ANDROID)
+  // Initialize CrashMemoryMetricsReporterImpl in order to assure that memory
+  // allocation does not happen in OnOOMCallback.
+  CrashMemoryMetricsReporterImpl::Instance();
+#endif
 }
 
 }  // namespace