From 41b3ae9e8d2f0dffef0e83984856cd4669bdba52 Mon Sep 17 00:00:00 2001 From: "tony@chromium.org" Date: Mon, 5 Oct 2009 21:50:46 +0000 Subject: Up the new tab paint observer timeout from 2s to 5s. Trying to see if this gets us more accurate data on new tab times. BUG=21398 TBR=evanm (ok'ed in person) Review URL: http://codereview.chromium.org/257052 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@28050 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/dom_ui/new_tab_ui.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'chrome/browser') diff --git a/chrome/browser/dom_ui/new_tab_ui.cc b/chrome/browser/dom_ui/new_tab_ui.cc index 688377f..353f224 100644 --- a/chrome/browser/dom_ui/new_tab_ui.cc +++ b/chrome/browser/dom_ui/new_tab_ui.cc @@ -174,8 +174,8 @@ class PaintTimer : public RenderWidgetHost::PaintObserver { private: // The amount of time there must be no painting for us to consider painting - // finished. Observed times are in the ~1200ms range. - static const int kTimeoutMs = 2000; + // finished. Observed times are in the ~1200ms range on Windows. + static const int kTimeoutMs = 5000; // The time when we started benchmarking. base::TimeTicks start_; // The last time we got a paint notification. -- cgit v1.1