commit | d52adbcf3bc8f0216351feff956c936b387186b7 | [log] [tgz] |
---|---|---|
author | Scott Haseley <shaseley@chromium.org> | Mon May 16 19:21:47 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 16 19:21:47 2022 |
tree | b7cb8479dd1503d9c9a387b46baaea1aa45fb7a4 | |
parent | 8480ea6ad3d8ca4d67ae99d3eb3e45445d89607a [diff] |
Scheduler: Filter out continuous input for kPrioritizeCompositingAfterInput Continuous input, when rAF-algined, hops through the input task queue before ultimately running in rAF. This means we need to do more filtering in the scheduler to only prioritize rendering after discrete inputs. This CL adds that filtering. This also moves the kPrioritizeCompositingAfterInput from OnTaskComplete() to MaybeUpdateCompositorTaskQueuePriorityOnTaskCompleted(), consolidating the logic to update compositor priority after a task runs. (cherry picked from commit c528d652aa8aa3ce6267dfcfe3b406b60122781f) Bug: 853771, 1068426 Change-Id: Ifd3d00440688b015015d7d20320de330a70db376 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3641430 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Reviewed-by: Minoru Chikamune <chikamune@chromium.org> Commit-Queue: Scott Haseley <shaseley@chromium.org> Reviewed-by: Dave Tapuska <dtapuska@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1002987} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3648579 Auto-Submit: Scott Haseley <shaseley@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5060@{#23} Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.