[Android WebView] Fix the startup sequence for in-process mode.

The GpuDataManager should be initialized before SetRunRendererInProcess to ensure
the gpu features/blacklists are correctly set for renderer.

BUG=468150

Review URL: https://codereview.chromium.org/1015633003

Cr-Commit-Position: refs/heads/master@{#321258}

content/browser/browser_main_loop.cc

@@ -614,13 +614,6 @@ int BrowserMainLoop::PreCreateThreads() {
   }
 #endif
 
-#if !defined(OS_IOS) && (!defined(GOOGLE_CHROME_BUILD) || defined(OS_ANDROID))
-  // Single-process is an unsupported and not fully tested mode, so
-  // don't enable it for official Chrome builds (except on Android).
-  if (parsed_command_line_.HasSwitch(switches::kSingleProcess))
-    RenderProcessHost::SetRunRendererInProcess(true);
-#endif
-
   // Need to initialize in-process GpuDataManager before creating threads.
   // It's unsafe to append the gpu command line switches to the global
   // CommandLine::ForCurrentProcess object after threads are created.
@@ -640,6 +633,13 @@ int BrowserMainLoop::PreCreateThreads() {
       GpuDataManagerImpl::GetInstance()->Initialize();
   }
 
+#if !defined(OS_IOS) && (!defined(GOOGLE_CHROME_BUILD) || defined(OS_ANDROID))
+  // Single-process is an unsupported and not fully tested mode, so
+  // don't enable it for official Chrome builds (except on Android).
+  if (parsed_command_line_.HasSwitch(switches::kSingleProcess))
+    RenderProcessHost::SetRunRendererInProcess(true);
+#endif
+
   return result_code_;
 }