From 4d0892b08c7f42a433a278c05498d7c6ddbe8eeb Mon Sep 17 00:00:00 2001 From: chrishtr Date: Wed, 10 Feb 2016 22:22:46 -0800 Subject: Never call GraphicsLayer::paint when fetching painted output from cc. GraphicsLayer::paint may not be a no-op if there happened to be dirty layout or paint since the last time a synchronized paint occurred. BUG=585694 TBR=ajuma@chromium.org CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1690763003 Cr-Commit-Position: refs/heads/master@{#374864} --- cc/debug/rasterize_and_record_benchmark.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'cc/debug') diff --git a/cc/debug/rasterize_and_record_benchmark.cc b/cc/debug/rasterize_and_record_benchmark.cc index 59d1665..3a49ab6 100644 --- a/cc/debug/rasterize_and_record_benchmark.cc +++ b/cc/debug/rasterize_and_record_benchmark.cc @@ -125,7 +125,7 @@ void RasterizeAndRecordBenchmark::RunOnLayer(PictureLayer* layer) { mode_index < DisplayListRecordingSource::RECORDING_MODE_COUNT; mode_index++) { ContentLayerClient::PaintingControlSetting painting_control = - ContentLayerClient::PAINTING_BEHAVIOR_NORMAL; + ContentLayerClient::PAINTING_BEHAVIOR_NORMAL_FOR_TEST; switch ( static_cast(mode_index)) { case DisplayListRecordingSource::RECORD_NORMALLY: -- cgit v1.1