[PE] Don't allow raster tasks for pre-paint tiles with at-raster images.
In GPU raster mode, only one raster task can be active at a time. This means that these rasters have to happen quickly, or they will block other work. For this reason, we should not allow pre-paint GPU raster tasks which might have very slow performance to execute, because otherwise they will block future high-priority on-screen raster tasks. Raster tasks can have at-raster image decoding if the memory for storing pre-decoded images has been exhausted. This is the case in the website referenced in the bug. In these cases, rather than allowing the raster to proceed and potentially jank display due to long image decodes, we abort the raster, but still proceed with the image decodes (which don't block other raster, and may be useful to decode in any case). Bug: 768799 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I2ec78361739b7b8f455f26211f21a5f8e995a8b6 Reviewed-on: https://chromium-review.googlesource.com/806855 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by:Khushal <khushalsagar@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#521975}
Showing
Please register or sign in to comment