25f8dc29afb7f8f6961a3641c8c44af0cd3a20ed - chromium/src

commit	25f8dc29afb7f8f6961a3641c8c44af0cd3a20ed	[log] [tgz]
author	jorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>	Wed Nov 18 11:07:40 2009
committer	jorlow@chromium.org <jorlow@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>	Wed Nov 18 11:07:40 2009
tree	535ff796c06936473c6698c8cdee840deecc058d
parent	8e557d663d30c46bc87e4dd3dffa8e13457588c5 [diff]

Make the WebKitThread object start the WebKit thread on construction (not lazily).

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.

TEST=The WebKit thread gets spun up early in the initialization process.
BUG=24144

Review URL: http://codereview.chromium.org/405007

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32319 0039d316-1c4b-4281-b951-d872f2087c98

chrome/browser/in_process_webkit/dom_storage_dispatcher_host.cc[diff]
chrome/browser/in_process_webkit/dom_storage_dispatcher_host.h[diff]
chrome/browser/in_process_webkit/webkit_thread.cc[diff]
chrome/browser/in_process_webkit/webkit_thread.h[diff]

4 files changed

tree: 535ff796c06936473c6698c8cdee840deecc058d