[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
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 project 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.
All DevTools commits: View the log or follow @DevToolsCommits on Twitter
All open DevTools tickets on crbug.com
File a new DevTools ticket: new.crbug.com
Code reviews mailing list: [email protected]
@ChromeDevTools on Twitter
Chrome DevTools mailing list: groups.google.com/forum/google-chrome-developer-tools