Backing out release build autoreg optimization. The optimization fails

if people pull a more recent build on top of their existing one.
- approved by Chris Hofmann


git-svn-id: svn://10.0.0.236/trunk@39003 18797224-902f-48f8-a5cc-f745e15eee43

mozilla/xpfe/bootstrap/nsSetupRegistry.cpp

@@ -31,7 +31,6 @@
 #include "nsFileLocations.h"
 #include "nsIFileLocator.h"
 #include "nsIFileSpec.h"
-#include "nsSpecialSystemDirectory.h"
 
 #include "nsAppCoresCIDs.h"
 #include "nsIDOMAppCoresManager.h"
@@ -85,17 +84,6 @@ static NS_DEFINE_CID(kWindowMediatorCID,  NS_WINDOWMEDIATOR_CID);
 
 nsresult NS_AutoregisterComponents()
 {
-  // Dont run Autoregistration at startup if this is a release build and
-  // the component registry already exist. For debug builds we still run
-  // autoreg because developers change components that might require
-  // reregistration.
-#ifndef DEBUG
-  nsSpecialSystemDirectory componentRegistry(nsSpecialSystemDirectory::XPCOM_CurrentProcessComponentRegistry);
-  if (componentRegistry.Exists() == PR_TRUE)
-  {
-    return NS_OK;
-  }
-#endif /* !DEBUG */
   nsresult rv = nsComponentManager::AutoRegister(nsIComponentManager::NS_Startup,
                                                  NULL /* default */);
   return rv;