[M127][ve] Fix memory leak in the Non-DOM state

The leak happens because we register non-DOM child loggables for some DOM nodes that never appear in the view port. Previous implementation used to hold strong references to both the child and the parent, which was released when child impression was logged. Since this is not guaranteed to happen, we might accumulate lots of such entries.

Current code stores non-DOM loggables in a weak map keyed by parent, so that they all could be released as soon as parent is released.

Bug: 352496178
Change-Id: If32ff440b95226a4c6eec5742917e1773844654c
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5713929
Auto-Submit: Danil Somsikov <[email protected]>
Commit-Queue: Danil Somsikov <[email protected]>
Reviewed-by: Yang Guo <[email protected]>
(cherry picked from commit b3cda0381251db9d1de66bbad39251f183f24c94)
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5712843
4 files changed
tree: 70a9e38c77b7e6f63c600c42fad3d8443ebf7a31
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. extensions/
  7. front_end/
  8. inspector_overlay/
  9. node_modules/
  10. scripts/
  11. test/
  12. third_party/
  13. v8/
  14. .clang-format
  15. .editorconfig
  16. .eslintignore
  17. .eslintrc.js
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .gitmodules
  22. .gn
  23. .mailmap
  24. .npmignore
  25. .npmrc
  26. .style.yapf
  27. .stylelintignore
  28. .stylelintrc.json
  29. AUTHORS
  30. BUILD.gn
  31. codereview.settings
  32. DEPS
  33. LICENSE
  34. OWNERS
  35. package-lock.json
  36. package.json
  37. PRESUBMIT.py
  38. README.md
  39. tsconfig.json
  40. 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 project documentation for instructions to set up, use, and maintain a DevTools front-end checkout, as well as design guidelines, and architectural documentation.

Additional references

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