diff options
| author | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-01-31 17:37:54 +0000 |
|---|---|---|
| committer | sky@chromium.org <sky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-01-31 17:37:54 +0000 |
| commit | 49922313bd7d5deb2479001f9646e7fa23d7ec25 (patch) | |
| tree | 2fc8de8aa732fd30e2e6a125dab292cd67c87d0e /chrome/renderer/render_widget_fullscreen_pepper.cc | |
| parent | f3583ec80bcd9e3f561a2596924194a8e9c6d92e (diff) | |
| download | chromium_src-49922313bd7d5deb2479001f9646e7fa23d7ec25.zip chromium_src-49922313bd7d5deb2479001f9646e7fa23d7ec25.tar.gz chromium_src-49922313bd7d5deb2479001f9646e7fa23d7ec25.tar.bz2 | |
Couple of changes in hopes of finally making ShareProcessesOnRestore
not flakey. Here's the set of changes:
. Before getting the process count we wait for the PROCESS_LAUNCHER
thread to go idle. On linux we push process shutdown to the
PROCESS_LAUNCHER thread. So, it's important we wait for this thread
to process all requests before getting the process count.
. Makes TabRestore take a boolean indicating if it succeeded.
. Change IDC_NEW_TAB from waiting for INITIAL_NEW_TAB_UI_LOAD to
waiting until the tab loads. INITIAL_NEW_TAB_UI_LOAD isn't really a
good indication that the new tab has finished loading.
A key part of making this test not flakey is
http://codereview.chromium.org/6398005/, but that'll be landed
separately.
BUG=52022
TEST=none
Review URL: http://codereview.chromium.org/6263018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@73156 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/renderer/render_widget_fullscreen_pepper.cc')
0 files changed, 0 insertions, 0 deletions