Change for building font cache into separate thread inside utility process.

Change for building font cache into separate thread inside utility process so that IO thread remains responsive.

BUG=458751, 436195
R=cpu,scottmg

Committed: https://crrev.com/e229ed0f0f2d4bab94fe4afb1213f7ddd6756d63
Cr-Commit-Position: refs/heads/master@{#320983}

[scottmg, 2015-03-17 05:28:17]

https://codereview.chromium.org/1011023002/diff/1/chrome/utility/font_cache_h...
File chrome/utility/font_cache_handler_win.cc (right):

https://codereview.chromium.org/1011023002/diff/1/chrome/utility/font_cache_h...
chrome/utility/font_cache_handler_win.cc:26: utility_task_runner_ =
base::MessageLoop::current()->message_loop_proxy();
This is in preparation for a cancellation message? Maybe it'd be better to split
this out into the CL that adds that, and just land the timing change in this CL.

[Shrikant Kelkar, 2015-03-17 19:54:40]

On 2015/03/17 05:28:17, scottmg wrote:
>
https://codereview.chromium.org/1011023002/diff/1/chrome/utility/font_cache_h...
> File chrome/utility/font_cache_handler_win.cc (right):
> 
>
https://codereview.chromium.org/1011023002/diff/1/chrome/utility/font_cache_h...
> chrome/utility/font_cache_handler_win.cc:26: utility_task_runner_ =
> base::MessageLoop::current()->message_loop_proxy();
> This is in preparation for a cancellation message? Maybe it'd be better to
split
> this out into the CL that adds that, and just land the timing change in this
CL.

removed delay cache building from this change. ptal.

[cpu_(ooo_6.6-7.5), 2015-03-17 20:40:43]

lgtm

https://codereview.chromium.org/1011023002/diff/20001/chrome/utility/font_cac...
File chrome/utility/font_cache_handler_win.cc (right):

https://codereview.chromium.org/1011023002/diff/20001/chrome/utility/font_cac...
chrome/utility/font_cache_handler_win.cc:29: cache_thread_.reset(new
base::Thread("cache_thread"));
use "font_cache_tread"

[Shrikant Kelkar, 2015-03-17 20:43:13]

https://codereview.chromium.org/1011023002/diff/20001/chrome/utility/font_cac...
File chrome/utility/font_cache_handler_win.cc (right):

https://codereview.chromium.org/1011023002/diff/20001/chrome/utility/font_cac...
chrome/utility/font_cache_handler_win.cc:29: cache_thread_.reset(new
base::Thread("cache_thread"));
On 2015/03/17 20:40:43, cpu wrote:
> use "font_cache_tread"

Done.

[Shrikant Kelkar, 2015-03-17 20:43:17]

The CQ bit was checked by shrikant@chromium.org

[Shrikant Kelkar, 2015-03-17 20:43:18]

The patchset sent to the CQ was uploaded after l-g-t-m from cpu@chromium.org
Link to the patchset: https://codereview.chromium.org/1011023002/#ps40001
(title: "Changed thread name.")

[commit-bot: I haz the power, 2015-03-17 20:44:26]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1011023002/40001

[commit-bot: I haz the power, 2015-03-17 21:47:22]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-03-17 21:48:45]

Patchset 3 (id:??) landed as
https://crrev.com/e229ed0f0f2d4bab94fe4afb1213f7ddd6756d63
Cr-Commit-Position: refs/heads/master@{#320983}