Timeline: Render threads containing only CPU profile samples RendererHandler skipped threads without renderer trace events during tree construction. CPU profile samples on these threads (such as WebAssembly background execution) were omitted from process.threads and missing from the Performance panel. Ensure CPU profile threads present in SamplesHandler are added to processes in RendererHandler and processed after profile call injection. Unskip WASM performance profiling E2E test. Fixed: 537672763 TAG=agy CONV=8abb05c5-df7d-4ea3-9e85-70bcbb786491 Change-Id: Ibb6c607362d8aa51c6494a700159accce30bf423 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/8159380 Reviewed-by: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.
The frontend is available on chromium.googlesource.com. Check out the Chromium DevTools documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.
DevTools frontend repository is mirrored on GitHub.
DevTools frontend is also available on NPM as the chrome-devtools-frontend package. It's not currently available via CJS or ES modules, so consuming this package in other tools may require some effort.
The version number of the npm package (e.g. 1.0.373466) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
There are a few options to keep an eye on the latest and greatest of DevTools development:
Follow What's new in DevTools.
Follow Umar's Dev Tips.
Follow these individual Twitter accounts: @umaar, @malyw, @kdzwinel, @addyosmani, @paul_irish, @samccone, @mathias, @mattzeunert, @PrashantPalikhe, @ziyunfei, and @bmeurer.
Follow to g/devtools-reviews@chromium.org mailing list for all reviews of pending code, and view the log, or follow @DevToolsCommits on Twitter.
Checkout all open DevTools tickets on crbug.com
Use Chrome Canary and poke around the experiments.