Fixed RLZTracker::GetAccessPointRlz to route IO calls to the FILE thread.

chrome/browser/search_engines/search_terms_data.cc

Index: chrome/browser/search_engines/search_terms_data.cc
diff --git a/chrome/browser/search_engines/search_terms_data.cc b/chrome/browser/search_engines/search_terms_data.cc
index 7b09df250d341af308dbe6632a9ba629128f58ba..3e80c7f4fae2072c6539ba867e740fc9f13cfd00 100644
--- a/chrome/browser/search_engines/search_terms_data.cc
+++ b/chrome/browser/search_engines/search_terms_data.cc
@@ -80,11 +80,13 @@ string16 UIThreadSearchTermsData::GetRlzParameterValue() const {
   // For organic brandcodes do not use rlz at all. Empty brandcode usually
   // means a chromium install. This is ok.
   string16 brand;
-  // See http://crbug.com/62337 .
-  base::ThreadRestrictions::ScopedAllowIO allow_io;
   if (GoogleUpdateSettings::GetBrand(&brand) && !brand.empty() &&
-      !GoogleUpdateSettings::IsOrganic(brand))
+      !GoogleUpdateSettings::IsOrganic(brand)) {
+    // This call will return false the first time(s) it is called until the
+    // value has been cached. This normally would mean that at most one omnibox
+    // search might not send the RLZ data but this is not really a problem.
     RLZTracker::GetAccessPointRlz(rlz_lib::CHROME_OMNIBOX, &rlz_string);
+  }
   return rlz_string;
 }
 #endif