commit | 1678187beec91f317fce8a7f6341d566e67640ef | [log] [tgz] |
---|---|---|
author | Austin Sullivan <asully@chromium.org> | Fri Mar 14 23:03:10 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 14 23:03:10 2025 |
tree | 0c81ba849690caf96759f542c18b872524043150 | |
parent | e0793a1f59b680e5cca6944f96278edf971e9d22 [diff] |
Revert "Move metric export off critical path." This reverts commit 4ab3028a991fcbe5ab9d1ec70404c1aef63efcae. Reason for revert: See https://crbug.com/403600081 Causing build failures on various ChromeOS bots Original change's description: > Move metric export off critical path. > > Refactor AsyncLayerTreeFrameSink so that metric export > occur at the end of a frame during either > SubmitCompositorFrame or DidNotPresent calls. > > This would greatly slim down the CPU cost of the > OnBeginFrame function, half of which is spent on metrics > as shown in Figure 2 of go/chrome-cc-metrics-refactor. > > Change-Id: I8cd3470d59b9bf6c4910237802add798d4eafb05 > Bug: 338977417 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6221595 > Reviewed-by: Jonathan Ross <jonross@chromium.org> > Commit-Queue: Stacy Gaikovaia <gaiko@google.com> > Cr-Commit-Position: refs/heads/main@{#1432772} Bug: 338977417, 403600081 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: I2f9ab44a38934f6ef4161d76f1efd27219b2f764 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6356883 Owners-Override: Austin Sullivan <asully@chromium.org> Auto-Submit: Austin Sullivan <asully@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1433029}
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.