commit | 52919f68e3f1ebc946d372232618512d0ec82de0 | [log] [tgz] |
---|---|---|
author | Jonathan Ross <jonross@chromium.org> | Thu Jan 25 17:28:49 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 25 17:28:49 2024 |
tree | 8d39aa0d0c2d5e4ab2623e6c4ab7fec40e0c752f | |
parent | 06f1357c6e08b20590d46a867aa0161466ace061 [diff] |
Remove the V1 cc metrics path The last of the usage of V1 metrics in ChromeOS was removed: https://chromium-review.googlesource.com/c/chromium/src/+/5213406 This change removes all of the path usage to calculate V1 metrics. Several signals are no longer needed by FrameSequenceTacker as we use the AddSortedFrame path for V3. This also removes old debugging traces that are no longer needed, with PipelineReporter being easier to follow. This should address the OoM seen in crbug.com/1518417 FrameSequenceTackerTest was overhauled to reflect the new signalling and AddSortedFrame post processing. This also removes V1 Graphics.Smoothness.*Stale as the final Finch using it launched. OBSOLETE_HISTOGRAM[Graphics.Smoothness.MaxStale]=finches complete, no longer needed OBSOLETE_HISTOGRAM[Graphics.Smoothness.Stale]=finches complete, no longer needed Bug: 1256879, 1518417 Change-Id: I526dec891fec850caeb5eb4e7e7305061b7c59be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5224910 Reviewed-by: Kyle Charbonneau <kylechar@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/main@{#1252174}
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.