Don't share renderers between unrelated tabs on Android.

content/browser/android/content_startup_flags.h

Index: content/browser/android/content_startup_flags.h
diff --git a/content/browser/android/content_startup_flags.h b/content/browser/android/content_startup_flags.h
index 836ea3c1206e181f28222951c9908d6a971d74d5..8f55a0c2cf46998b9102150a9ec2563145edbe53 100644
--- a/content/browser/android/content_startup_flags.h
+++ b/content/browser/android/content_startup_flags.h
@@ -12,7 +12,7 @@ namespace content {
 // Force-appends flags to the command line turning on Android-specific
 // features owned by Content. This is called as soon as possible during
 // initialization to make sure code sees the new flags.
-void SetContentCommandLineFlags(int max_render_process_count,
+void SetContentCommandLineFlags(bool single_process,

[johnme, 2014/07/17 11:28:20]

In the .cc this is called "in_process", whereas here it's called
"single_process"?

In general I find the name in_process quite confusing - it's not obvious what
"starting a browser process in process" means; why not just always call it
single_process, since single process mode has a well-known and fairly intuitive
meaning?

[ppi, 2014/07/18 11:13:17]

Done.

                                 const std::string& plugin_descriptor);
 
 }  // namespace content