Use TaskScheduler instead of blocking pool in wallpaper_manager.cc.
The following traits are used: Priority: Inherited (default) The priority is inherited from the calling context (i.e. TaskTraits are initialized with the priority of the current task). Shutdown behavior: SKIP_ON_SHUTDOWN (default) Tasks posted with this mode that have not started executing at shutdown will never run. However, any task that has already begun executing when shutdown is invoked will be allowed to continue and will block shutdown until completion. Note: Previously, the task was posted to the blocking pool with BLOCK_SHUTDOWN (default in SequencedWorkerPool). May Block: Tasks posted with MayBlock() may block. This includes but is not limited to tasks that wait on synchronous file I/O operations: read or write a file from disk, interact with a pipe or a socket, rename or delete a file, enumerate files in a directory, etc. This trait isn't required for the mere use of locks. BUG=667892 Review-Url: https://codereview.chromium.org/2627083005 Cr-Commit-Position: refs/heads/master@{#443261}
Showing
Please register or sign in to comment