Do not load extension system in the Profile import process.

content/public/common/content_switches.cc

Index: content/public/common/content_switches.cc
diff --git a/content/public/common/content_switches.cc b/content/public/common/content_switches.cc
index b551191703d657acfc5483116bfbbde574efb283..211bb8dd21e9626fd63016a858ccefae17a49696 100644
--- a/content/public/common/content_switches.cc
+++ b/content/public/common/content_switches.cc
@@ -464,6 +464,9 @@ const char kInProcessWebGL[]                = "in-process-webgl";
 // Specifies the flags passed to JS engine
 const char kJavaScriptFlags[]               = "js-flags";
 
+// Specifies whether a forked browser process should always run BrowserMain.
+const char kLaunchAsBrowser[]               = "as-browser";

[Jói, 2012/12/17 13:46:16]

It feels a bit weird to promote this to a publicly-available switch since it is
only checked by test code AFAIU.  Is there no way to add the flag on the Chrome
side only in test code (which is already allowed to use content/public/test,
where this flag was originally defined)?

[tapted, 2012/12/18 02:25:58]

I've put up an alternative that removes the changes in content/public by adding
new, generic interfaces to first_run. Let me know what you think.

+
 // Load an NPAPI plugin from the specified path.
 const char kLoadPlugin[]                    = "load-plugin";