Don't use base::MessageLoop::{Quit,QuitClosure} in chrome/

chrome/test/base/in_process_browser_test.h

Index: chrome/test/base/in_process_browser_test.h
diff --git a/chrome/test/base/in_process_browser_test.h b/chrome/test/base/in_process_browser_test.h
index 9192ec2288b61919268b6a71faf66f79bece4f34..06c0b61339853ba1000dca8a2a105d1b92fae04d 100644
--- a/chrome/test/base/in_process_browser_test.h
+++ b/chrome/test/base/in_process_browser_test.h
@@ -51,8 +51,8 @@ class ContentRendererClient;
 //   state changes you'll need to run the message loop from your test method.
 //   For example, if you need to wait till a find bar has completely been shown
 //   you'll need to invoke content::RunMessageLoop. When the message bar is
-//   shown, invoke MessageLoop::current()->Quit() to return control back to your
-//   test method.
+//   shown, invoke MessageLoop::current()->QuitWhenIdle() to return control back
+//   to your test method.
 // . If you subclass and override SetUp, be sure and invoke
 //   InProcessBrowserTest::SetUp. (But see also SetUpOnMainThread,
 //   SetUpInProcessBrowserTestFixture and other related hook methods for a