Remove ContentViewCore.enableMultiProcess etc.

content/public/android/java/src/org/chromium/content/browser/ContentView.java

Index: content/public/android/java/src/org/chromium/content/browser/ContentView.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/ContentView.java b/content/public/android/java/src/org/chromium/content/browser/ContentView.java
index e0639b7239680786585db13b663a0b93b656b9d9..ef6b27cfdb1c2dc1c8cead2da18904a7e02e012f 100644
--- a/content/public/android/java/src/org/chromium/content/browser/ContentView.java
+++ b/content/public/android/java/src/org/chromium/content/browser/ContentView.java
@@ -42,54 +42,6 @@ public class ContentView extends FrameLayout implements ContentViewCore.Internal
     // Used for Chrome.
     public static final int PERSONALITY_CHROME = ContentViewCore.PERSONALITY_CHROME;
 
-    /**
-     * Automatically decide the number of renderer processes to use based on device memory class.
-     * */
-    public static final int MAX_RENDERERS_AUTOMATIC = AndroidBrowserProcess.MAX_RENDERERS_AUTOMATIC;
-    /**
-     * Use single-process mode that runs the renderer on a separate thread in the main application.
-     */
-    public static final int MAX_RENDERERS_SINGLE_PROCESS =
-            AndroidBrowserProcess.MAX_RENDERERS_SINGLE_PROCESS;
-    /**
-     * Cap on the maximum number of renderer processes that can be requested.
-     */
-    public static final int MAX_RENDERERS_LIMIT = AndroidBrowserProcess.MAX_RENDERERS_LIMIT;
-
-    /**
-     * Enable multi-process ContentView. This should be called by the application before
-     * constructing any ContentView instances. If enabled, ContentView will run renderers in
-     * separate processes up to the number of processes specified by maxRenderProcesses. If this is
-     * not called then the default is to run the renderer in the main application on a separate
-     * thread.
-     *
-     * @param context Context used to obtain the application context.
-     * @param maxRendererProcesses Limit on the number of renderers to use. Each tab runs in its own
-     * process until the maximum number of processes is reached. The special value of
-     * MAX_RENDERERS_SINGLE_PROCESS requests single-process mode where the renderer will run in the
-     * application process in a separate thread. If the special value MAX_RENDERERS_AUTOMATIC is
-     * used then the number of renderers will be determined based on the device memory class. The
-     * maximum number of allowed renderers is capped by MAX_RENDERERS_LIMIT.
-     * @return Whether the process actually needed to be initialized (false if already running).
-     */
-    public static boolean enableMultiProcess(Context context, int maxRendererProcesses)
-            throws ProcessInitException {
-        return ContentViewCore.enableMultiProcess(context, maxRendererProcesses);
-    }
-
-    /**
-     * Initialize the process as the platform browser. This must be called before accessing
-     * ContentView in order to treat this as a Chromium browser process.
-     *
-     * @param context Context used to obtain the application context.
-     * @param maxRendererProcesses Same as ContentView.enableMultiProcess()
-     * @return Whether the process actually needed to be initialized (false if already running).
-     */
-    public static boolean initChromiumBrowserProcess(Context context, int maxRendererProcesses)
-            throws ProcessInitException {
-        return ContentViewCore.initChromiumBrowserProcess(context, maxRendererProcesses);
-    }
-
     private ContentViewCore mContentViewCore;
 
     /**