Use TaskScheduler instead of blocking pool in user_policy_manager_factory_chromeos.cc.

chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc

Index: chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc
diff --git a/chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc b/chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc
index 850b9b0234ea459f42bce7ba8968c7622a19cee8..ccbba21bda0bd30352dec60703d1c29207e64505 100644
--- a/chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc
+++ b/chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc
@@ -14,7 +14,7 @@
 #include "base/memory/ref_counted.h"
 #include "base/path_service.h"
 #include "base/sequenced_task_runner.h"
-#include "base/threading/sequenced_worker_pool.h"
+#include "base/task_scheduler/post_task.h"
 #include "base/threading/thread_task_runner_handle.h"
 #include "base/time/time.h"
 #include "chrome/browser/browser_process.h"
@@ -240,8 +240,9 @@ UserPolicyManagerFactoryChromeOS::CreateManagerForProfile(
           is_active_directory);
 
   scoped_refptr<base::SequencedTaskRunner> backend_task_runner =
-      content::BrowserThread::GetBlockingPool()->GetSequencedTaskRunner(
-          content::BrowserThread::GetBlockingPool()->GetSequenceToken());
+      base::CreateSequencedTaskRunnerWithTraits(
+          base::TaskTraits().MayBlock().WithPriority(
+              base::TaskPriority::BACKGROUND));

[Thiemo Nagel, 2017/04/27 09:44:52]

I think we should SKIP_ON_SHUTDOWN.  From what I can see, no data is lost if we
drop something on the floor as we can always re-fetch during the next session.

[fdoray, 2017/04/27 13:27:21]

Done.

   scoped_refptr<base::SequencedTaskRunner> io_task_runner =
       content::BrowserThread::GetTaskRunnerForThread(
           content::BrowserThread::IO);