diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-20 22:18:45 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-20 22:18:45 +0000 |
| commit | 6e948a40ee9134cfba48eb6d007378a4f4c11a8d (patch) | |
| tree | de4f6ec194b99f162e612462805692ba9445f35d /chrome/browser/cocoa/bookmark_bar_controller.mm | |
| parent | d7fc97946625fee2c54e18bce4f61608efeeef03 (diff) | |
| download | chromium_src-6e948a40ee9134cfba48eb6d007378a4f4c11a8d.zip chromium_src-6e948a40ee9134cfba48eb6d007378a4f4c11a8d.tar.gz chromium_src-6e948a40ee9134cfba48eb6d007378a4f4c11a8d.tar.bz2 | |
Revert 32608 - RESUBMIT of http://src.chromium.org/viewvc/chrome?view=rev&revision=32319 with unit test fixes.
Reverting this as this caused a number of valgrind test failures.
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/404025
TBR=jorlow@chromium.org
Review URL: http://codereview.chromium.org/427001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32687 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/cocoa/bookmark_bar_controller.mm')
0 files changed, 0 insertions, 0 deletions