commit | d0bf5fcd130a18a132a8d4ae97ec923df7cb8c16 | [log] [tgz] |
---|---|---|
author | François Doray <fdoray@chromium.org> | Mon Dec 02 19:54:53 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 02 19:54:53 2024 |
tree | ce0026fdccbd9bcd13f1a51e19b4d71e15055294 | |
parent | 7e1bc52f369d2e3db4ecd21ad9045796d02f23b8 [diff] |
Enable ScriptedIdleTaskControllerOOMFix by default. go/finch50-scripted-idle-task-controller-oom-fix No regression. We did not observe the expected movement to number of crashed clients. We want to land this anyways because it fixes an issue with timeouts not being honored: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/scheduler/scripted_idle_task_controller.cc;l=245-248;drc=9676dcbe427307e82bf4ce4424e8d8e7bfda7088 It seems that there are still many cases in which the number of "scheduler idle tasks" exceeds the number of "idle tasks". This could be because most "idle tasks" have been canceled (this does not cancel the corresponding "scheduler idle tasks"). Example: go/sample-crash-many-scheduler-idle-tasks-few-idle-tasks, see crash keys tab. The feature will be cleaned up in M134. Bug: 365114039 Change-Id: I1589e95d221267b1d06fbe8c7a87ec9793afe05a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6049852 Reviewed-by: Scott Haseley <shaseley@chromium.org> Commit-Queue: Scott Haseley <shaseley@chromium.org> Auto-Submit: Francois Pierre Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/main@{#1390523}
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.