Google Git
Sign in
chromium / devtools / devtools-frontend / 2ec237cea2f63f07659729f2c84a004900b87fb6
commit2ec237cea2f63f07659729f2c84a004900b87fb6[log] [tgz]
authorSimon Zünd <[email protected]>Thu Jul 17 05:30:52 2025
committerDevtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 17 08:21:56 2025
tree320220c72139c2c88a75f3df5eaca30654496e12
parent4f035ae08081a9e198fbe79af824c5d08376fa72 [diff]
[network] Allow NetworkRequetNodes to be gc'ed when the log is cleared

The network panel currently associates each NetworkRequest with it's
UI data grid node via a WeakMap. But since the ResourceTreeModel never
frees up NetworkRequests, we keep every <tr> of the Network panel alive
indefinitely.

This CL fixes at least the DOM element leak: When the view is reset,
we also reset the WeakMap. While we keep the NetworkRequests around
for now, at least we no longer keep detached DOM nodes around
indefinitely.

Drive-by: Make the module global a class member.

[email protected]

Bug: 390559089
Change-Id: I014ec2c56bab20f6c48c85cb205476860ea5c829
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6759714
Auto-Submit: Simon Zünd <[email protected]>
Reviewed-by: Philip Pfaffe <[email protected]>
Commit-Queue: Simon Zünd <[email protected]>
1 file changed
tree: 320220c72139c2c88a75f3df5eaca30654496e12
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. config/
  5. docs/
  6. extension-api/
  7. extensions/
  8. front_end/
  9. inspector_overlay/
  10. node_modules/
  11. scripts/
  12. test/
  13. third_party/
  14. v8/
  15. build
  16. buildtools
  17. .clang-format
  18. .clang-format-ignore
  19. .editorconfig
  20. .git-blame-ignore-revs
  21. .gitallowed
  22. .gitattributes
  23. .gitignore
  24. .gitmodules
  25. .gn
  26. .mailmap
  27. .npmignore
  28. .npmrc
  29. .style.yapf
  30. .stylelintignore
  31. .stylelintrc.json
  32. AUTHORS
  33. BUILD.gn
  34. codereview.settings
  35. CONTRIBUTING.md
  36. DEPS
  37. DIR_METADATA
  38. eslint.config.mjs
  39. favicon.ico
  40. LICENSE
  41. OWNERS
  42. package-lock.json
  43. package.json
  44. PRESUBMIT.py
  45. README.md
  46. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

The client-side of the Chrome DevTools, including all TypeScript & CSS to run the DevTools webapp.

Source code and documentation

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.

Source mirrors

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.

Getting in touch

There are a few options to keep an eye on the latest and greatest of DevTools development: