Change the new-task-manager flag so that the new implementation is enabled by default for all users.

chrome/browser/extensions/api/processes/processes_apitest.cc

Index: chrome/browser/extensions/api/processes/processes_apitest.cc
diff --git a/chrome/browser/extensions/api/processes/processes_apitest.cc b/chrome/browser/extensions/api/processes/processes_apitest.cc
index 34f8afb756352d2829d7f7051b0327923abf48c7..f2672ce6bb308d21a464df2e7a874fe389430564 100644
--- a/chrome/browser/extensions/api/processes/processes_apitest.cc
+++ b/chrome/browser/extensions/api/processes/processes_apitest.cc
@@ -18,6 +18,10 @@ IN_PROC_BROWSER_TEST_F(ExtensionApiTest, DISABLED_Processes) {
 }
 
 IN_PROC_BROWSER_TEST_F(ExtensionApiTest, ProcessesVsTaskManager) {
+  // This test is for the old implementation of the task manager. We must
+  // explicitly disable the new one.
+  task_manager::browsertest_util::EnableOldTaskManager();
+
   // Ensure task manager is not yet updating
   TaskManagerModel* model = TaskManager::GetInstance()->model();
   EXPECT_EQ(0, model->update_requests_);