TestBrowserThreads must outlive TestProfiles and TestProfileManagers

chrome/browser/sessions/session_restore_stats_collector_unittest.cc

Index: chrome/browser/sessions/session_restore_stats_collector_unittest.cc
diff --git a/chrome/browser/sessions/session_restore_stats_collector_unittest.cc b/chrome/browser/sessions/session_restore_stats_collector_unittest.cc
index 26e25db2146de30fdcf492d33251f7727bda95e5..7e6e90e63c043e31a656394c83d0b799d5233736 100644
--- a/chrome/browser/sessions/session_restore_stats_collector_unittest.cc
+++ b/chrome/browser/sessions/session_restore_stats_collector_unittest.cc
@@ -296,8 +296,9 @@ class SessionRestoreStatsCollectorTest : public testing::Test {
   // Infrastructure needed for using the TestWebContentsFactory. These are
   // initialized once by the fixture and reused across unittests.
   base::MessageLoop message_loop_;
-  TestingProfile testing_profile_;
   content::TestBrowserThread ui_thread_;
+  // |ui_thread_| needs to still be alive when |testing_profile_| is destroyed.
+  TestingProfile testing_profile_;
 
   // A new web contents factory is generated per test. This automatically cleans
   // up any tabs created by previous tests.