summaryrefslogtreecommitdiffstats
path: root/ui/gfx/render_text_mac.cc
diff options
context:
space:
mode:
authordennisjeffrey@chromium.org <dennisjeffrey@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-07-23 16:21:57 +0000
committerdennisjeffrey@chromium.org <dennisjeffrey@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-07-23 16:21:57 +0000
commit6852fb0c12ca6789695927262912f287e7dd350e (patch)
treee82fb66b7fb6c5491decd3910c93c9fc0d1418f7 /ui/gfx/render_text_mac.cc
parent1fed59867bd9b8ea27d14c631f94c3c2ab830254 (diff)
downloadchromium_src-6852fb0c12ca6789695927262912f287e7dd350e.zip
chromium_src-6852fb0c12ca6789695927262912f287e7dd350e.tar.gz
chromium_src-6852fb0c12ca6789695927262912f287e7dd350e.tar.bz2
Chrome Endure tests forcefully clear ChromeDriver's node cache on each test iteration.
This is a temporary workaround to the problem of ChromeDriver continually growing a DOM node cache while Chrome Endure tests run (significantly impacting the results reported by Chrome Endure tests). There is a discussion with the WebDriver team about how to solve this problem in a better way within WebDriver itself, but for now this workaround should stabilize the Chrome Endure test results until a better solution is implemented. BUG=None TEST=Verified a Gmail Chrome Endure test did not reach steady state in DOM node count without this change, but did reach steady state with this change. NOTRY=true Review URL: https://chromiumcodereview.appspot.com/10795057 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147860 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/gfx/render_text_mac.cc')
0 files changed, 0 insertions, 0 deletions