Use TaskScheduler instead of blocking pool in device_commands_factory_chromeos.cc.

chrome/browser/chromeos/policy/remote_commands/device_commands_factory_chromeos.cc

Index: chrome/browser/chromeos/policy/remote_commands/device_commands_factory_chromeos.cc
diff --git a/chrome/browser/chromeos/policy/remote_commands/device_commands_factory_chromeos.cc b/chrome/browser/chromeos/policy/remote_commands/device_commands_factory_chromeos.cc
index de461e56db0059a85692878de1610db33a7bb758..0c70a1fba1b31c21c783293239eeb82637f3a93a 100644
--- a/chrome/browser/chromeos/policy/remote_commands/device_commands_factory_chromeos.cc
+++ b/chrome/browser/chromeos/policy/remote_commands/device_commands_factory_chromeos.cc
@@ -7,7 +7,7 @@
 #include <memory>
 
 #include "base/memory/ptr_util.h"
-#include "base/threading/sequenced_worker_pool.h"
+#include "base/task_scheduler/post_task.h"
 #include "chrome/browser/chromeos/policy/remote_commands/device_command_fetch_status_job.h"
 #include "chrome/browser/chromeos/policy/remote_commands/device_command_reboot_job.h"
 #include "chrome/browser/chromeos/policy/remote_commands/device_command_screenshot_job.h"
@@ -16,7 +16,6 @@
 #include "chromeos/dbus/dbus_thread_manager.h"
 #include "components/policy/core/common/remote_commands/remote_command_job.h"
 #include "components/policy/proto/device_management_backend.pb.h"
-#include "content/public/browser/browser_thread.h"
 
 namespace em = enterprise_management;
 
@@ -37,9 +36,9 @@ DeviceCommandsFactoryChromeOS::BuildJobForType(em::RemoteCommand_Type type) {
     case em::RemoteCommand_Type_DEVICE_SCREENSHOT:
       return base::WrapUnique<RemoteCommandJob>(
           new DeviceCommandScreenshotJob(base::MakeUnique<ScreenshotDelegate>(
-              content::BrowserThread::GetBlockingPool()->GetSequencedTaskRunner(
-                  content::BrowserThread::GetBlockingPool()
-                      ->GetSequenceToken()))));
+              base::CreateSequencedTaskRunnerWithTraits(
+                  base::TaskTraits().MayBlock().WithPriority(
+                      base::TaskPriority::BACKGROUND)))));

[Thiemo Nagel, 2017/04/27 09:48:43]

Same here, I think we should SKIP_ON_SHUTDOWN.  I don't see value in blocking
shutdown on screenshotting.

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

Done.

     case em::RemoteCommand_Type_DEVICE_SET_VOLUME:
       return base::WrapUnique<RemoteCommandJob>(
           new DeviceCommandSetVolumeJob());