Experimentally disable termination on heap corrruption in order to measure the contribution of this…

content/app/content_main_runner.cc

Index: content/app/content_main_runner.cc
diff --git a/content/app/content_main_runner.cc b/content/app/content_main_runner.cc
index f8f9a42e61baeff7088de40bdb76796fbd78aafc..81611c5e2c57f1fd07e240750e7a502fc1d6f9f2 100644
--- a/content/app/content_main_runner.cc
+++ b/content/app/content_main_runner.cc
@@ -554,7 +554,8 @@ class ContentMainRunnerImpl : public ContentMainRunner {
     is_initialized_ = true;
     delegate_ = params.delegate;
 
-    base::EnableTerminationOnHeapCorruption();
+    if (params.enable_termination_on_heap_corruption)
+      base::EnableTerminationOnHeapCorruption();

[grt (UTC plus 2), 2014/07/30 21:05:11]

if it's okay for this to happen on line 574 instead of here, consider doing
something like this down there after the AtExitManager has been created:

  if (delegate_ &&
!delegate_->ShouldExperimentallyDisableTerminateOnHeapCorruption()) {
    base::EnableTerminationOnHeapCorruption();
  }

i haven't understood exactly what's going on here, so maybe that's tricky to do,
but it would allow you to keep the ShouldFoo check in chrome-land but do the
heap corruption thing here early in content-land.

     base::EnableTerminationOnOutOfMemory();
 
     // The exit manager is in charge of calling the dtors of singleton objects.