Populate allocation size into OOM exception on Windows.

components/crash/content/app/run_as_crashpad_handler_win.cc

Index: components/crash/content/app/run_as_crashpad_handler_win.cc
diff --git a/components/crash/content/app/run_as_crashpad_handler_win.cc b/components/crash/content/app/run_as_crashpad_handler_win.cc
index e51cfd77e001452f2efe36fbd6f9d3dfcd87fd12..20be2d108cf68043bd69d11ccc3318d189d18c2d 100644
--- a/components/crash/content/app/run_as_crashpad_handler_win.cc
+++ b/components/crash/content/app/run_as_crashpad_handler_win.cc
@@ -10,6 +10,7 @@
 #include <vector>
 
 #include "base/command_line.h"
+#include "base/process/memory.h"
 #include "base/strings/string16.h"
 #include "base/strings/string_util.h"
 #include "base/strings/utf_string_conversions.h"
@@ -18,6 +19,10 @@
 namespace crash_reporter {
 
 int RunAsCrashpadHandler(const base::CommandLine& command_line) {
+  // Make sure this process terminates on OOM in the same mode as other Chrome
+  // processes.
+  base::EnableTerminationOnOutOfMemory();

[Mark Mentovai, 2017/02/06 18:22:39]

We should centralize all of the Chrome-specific crashpad_handler setup stuff in
one location. The other thing that we now do is call
SetupFallbackCrashHandling(). That happens in
chrome/app/chrome_exe_main_win.cc’s wWinMain(), should it also happen here?

[Sigurður Ásgeirsson, 2017/02/06 19:43:58]

I felt it was clearer to have the
SetupFallbackCrashHandling/RunFallbackCrashHandler incantations in the same
scope, but I'm happy to move the setup if you feel strongly about it.

+
   std::vector<base::string16> argv = command_line.argv();
   const base::string16 process_type = L"--type=";
   argv.erase(std::remove_if(argv.begin(), argv.end(),