commit | fe74038b7d6136c36585607aa3ea86a5b46c3720 | [log] [tgz] |
---|---|---|
author | Stacy Gaikovaia <gaiko@google.com> | Fri Mar 14 18:17:48 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 14 18:17:48 2025 |
tree | 8ab60a73e7447b9f18495c0e4d13db760df0073b | |
parent | 8715f96c5553970c4e3df2f12a817c14a24e9508 [diff] |
Export timing details after mojo call to viz. We want to do the work of exporting metrics to the client after dispatching the frame complete signal to Viz rather than before. Bug: 338977417 Change-Id: Id9f2a093ef985f565499b3e0bdfbcf623d4e0515 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6354046 Commit-Queue: Stacy Gaikovaia <gaiko@google.com> Reviewed-by: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/main@{#1432883}
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.