diff options
| author | jorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-25 14:07:01 +0000 |
|---|---|---|
| committer | jorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-25 14:07:01 +0000 |
| commit | 458d689228b12028f02d632c091ad1f637bbc15b (patch) | |
| tree | cb1f7c625b168477a9b6a3100f1da017ba893c2e /chrome/common/logging_chrome.cc | |
| parent | 44632cbf3d7daf8db4edcb61082000b857865049 (diff) | |
| download | chromium_src-458d689228b12028f02d632c091ad1f637bbc15b.zip chromium_src-458d689228b12028f02d632c091ad1f637bbc15b.tar.gz chromium_src-458d689228b12028f02d632c091ad1f637bbc15b.tar.bz2 | |
RESUBMIT of http://codereview.chromium.org/404025/show
Start the WebKit thread when we initialize the resource dispatcher host.
NOTE: It's very possible this will have a startup performance impact. I'm going to watch the bots after committing.
TODO: Clean up shutdown logic that exists simply because we don't know whether or not we'll ever start the WebKit thread.
TBR=darin
TEST=The WebKit thread gets spun up early in the initialization process.
BUG=24144,28364
Review URL: http://codereview.chromium.org/432007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33063 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/logging_chrome.cc')
0 files changed, 0 insertions, 0 deletions