Bind CompositingModeReporter to compositor task runner If fallback to software compositing occurs during browser startup (e.g. induced by cyclical gpu process crashes) existing renderers could hang in infinite post task loop starting from LayerTreeView::RequestNewLayerTreeFrameSink because of scheduling issues. Binding CompositorModeReporter mojo interface to compositor task runner fixes the problem Bug: 1278766 Change-Id: I6a1eade1f8a56756d3cf8d2877fabc881d265157 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3330283 Auto-Submit: Maxim Smirnov <smirnov-maxim@yandex-team.ru> Reviewed-by: danakj chromium <danakj@chromium.org> Commit-Queue: Maxim Smirnov <smirnov-maxim@yandex-team.ru> Cr-Commit-Position: refs/heads/main@{#953469}
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.