Compute retaining paths for object This CL adds a method getRetainingPaths to HeapSnapshotProxy. This method finds the paths from an object to the GC roots. Unlike the auto-expansion logic in the DevTools UI, it tries to find more than one path to the root. Finding all retaining paths can be useful to better understand from where the target object is kept alive. getRetainingPaths() performs a DFS search starting from a target node to the GC roots. For this it follows retainer edges of an object sorted by the precomputed distance field of each retaining object. The algorithm enforces limits on the recursion depth and the maximum number of nodes/siblings to visit. getRetainingPaths() also returns whether a limit (and which one) was reached during visitation. Bug: 497855658 Change-Id: Ifa3fbadfddee7e2c1e4d98e008014bef0e97252a Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7879915 Reviewed-by: Nikolay Vitkov <nvitkov@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Simon Zünd <szuend@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.