Use TaskScheduler instead of SequencedWorkerPool in storage_partition_impl_map.cc.

content/browser/storage_partition_impl_map.cc

Index: content/browser/storage_partition_impl_map.cc
diff --git a/content/browser/storage_partition_impl_map.cc b/content/browser/storage_partition_impl_map.cc
index 40004a9e3e6526b45ebcdd7344a039d025782cf1..4563fea015678f8632934f1e9a91462ec6898b7f 100644
--- a/content/browser/storage_partition_impl_map.cc
+++ b/content/browser/storage_partition_impl_map.cc
@@ -20,7 +20,6 @@
 #include "base/strings/string_util.h"
 #include "base/strings/stringprintf.h"
 #include "base/task_scheduler/post_task.h"
-#include "base/threading/sequenced_worker_pool.h"
 #include "base/threading/thread_task_runner_handle.h"
 #include "build/build_config.h"
 #include "content/browser/appcache/appcache_interceptor.h"
@@ -371,12 +370,9 @@ base::FilePath StoragePartitionImplMap::GetStoragePartitionPath(
 StoragePartitionImplMap::StoragePartitionImplMap(
     BrowserContext* browser_context)
     : browser_context_(browser_context),
-      resource_context_initialized_(false) {
-  // Doing here instead of initializer list cause it's just too ugly to read.
-  base::SequencedWorkerPool* blocking_pool = BrowserThread::GetBlockingPool();
-  file_access_runner_ =
-      blocking_pool->GetSequencedTaskRunner(blocking_pool->GetSequenceToken());
-}
+      file_access_runner_(base::CreateSequencedTaskRunnerWithTraits(

[jam, 2017/05/18 14:20:14]

just to double check: this doesn't create a unique thread right? (would be good
to make this clear in the comments for the method)

[fdoray, 2017/05/18 14:51:24]

No, it doesn't create a new thread. I will make this clearer in the
documentation.

+          {base::MayBlock(), base::TaskPriority::BACKGROUND})),
+      resource_context_initialized_(false) {}
 
 StoragePartitionImplMap::~StoragePartitionImplMap() {
 }