| commit | 2878995f1fc8296c697818a5b2ce7c8cec65ebea | [log] [tgz] |
|---|---|---|
| author | Markus Handell <handellm@google.com> | Fri Oct 14 07:32:09 2022 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 14 07:32:09 2022 |
| tree | ad0b2767e0ee5c4325bab64a49ef6c3e578483fd | |
| parent | a4dde50d180ab8888ab63bed2b44d510a334b144 [diff] |
Stop assuming the Media task runner is a thread. Code generally assumes the Media task runner is a single thread. Issue crbug.com/1144329 hints at there isn't a hard requirement that the Media sequence is a thread, and additional motivation for changing has been provided in crbug.com/1144329#c2 (power consumption). This change should be NOP, but hoists build assumptions on Media being a SingleThreadTaskRunner to being its super class, SequencedTaskRunner. Future CLs will be landed to also fix runtime dependencies as the Media thread switches to become sourced by CreateSequencedTaskRunner() inside RenderThreadImpl. Bug: 1144329 Change-Id: Id24ffd3c059a9e5da567861758500c171031fd36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3928266 Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Reviewed-by: Dan Sanders <sandersd@chromium.org> Reviewed-by: Jordan Bayles <jophba@chromium.org> Reviewed-by: Sean Topping <seantopping@chromium.org> Commit-Queue: Markus Handell <handellm@google.com> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1059135}
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.