Fix TestBrowserThread destruction order in CrOS tests.

chrome/browser/chromeos/file_manager/file_tasks_unittest.cc

Index: chrome/browser/chromeos/file_manager/file_tasks_unittest.cc
diff --git a/chrome/browser/chromeos/file_manager/file_tasks_unittest.cc b/chrome/browser/chromeos/file_manager/file_tasks_unittest.cc
index a013bd9585dc6be2aeea4de45302a857ccaa83b0..b66802f5814860d5b7409f1e3030f28a1a7672a8 100644
--- a/chrome/browser/chromeos/file_manager/file_tasks_unittest.cc
+++ b/chrome/browser/chromeos/file_manager/file_tasks_unittest.cc
@@ -167,10 +167,12 @@ TEST(FileManagerFileTasksTest, ParseTaskID_UnknownTaskType) {
 }
 
 TEST(FileManagerFileTasksTest, FindDriveAppTasks) {
-  TestingProfile profile;
-  // For DriveAppRegistry, which checks CurrentlyOn(BrowserThread::UI).
+  // For DriveAppRegistry and TestingProfile, which check
+  // CurrentlyOn(BrowserThread::UI).
   content::TestBrowserThreadBundle thread_bundle;
 
+  TestingProfile profile;
+
   // Foo.app can handle "text/plain" and "text/html"
   std::unique_ptr<google_apis::AppResource> foo_app(
       new google_apis::AppResource);