Google GitGoogle Git
Sign in
chromium/devtools/devtools-frontend/refs/heads/chromium/5888
commit
69af6e8365fa863759d2c86d8c849ab2313cf8f1
[log]
author
Jack Franklin <jacktfranklin@google.com>
Thu Jul 13 14:25:26 2023
committer
Devtools-frontend LUCI CQ <devtools-frontend-scoped@luci-project-accounts.iam.gserviceaccount.com>
Thu Jul 13 15:29:00 2023
tree
2370bf07353e09077d055120bc104fae20461628
parent
cdd39e1a3b3e3643075dbc667b3abcbc9fb0dc55 [diff]
Ensure we resume all targets when performance tracing errors

If there is an error in the actual tracing, the TimelineController
should handle it and resume all targets. But because resumeAllTargets()
is safe to call multiple times (it no-ops if nothing is suspended), we
can also call it again if the try{} block in the TimelinePanel that
starts recording errors.

Fixed: 1462539
Change-Id: Ic52f72617447b955d02e512d18edade76293676e
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4683607
Commit-Queue: Nancy Li <nancyly@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Nancy Li <nancyly@chromium.org>
1 file changed
tree: 2370bf07353e09077d055120bc104fae20461628
  1. .vscode/
  2. build_overrides/
  3. config/
  4. docs/
  5. extension-api/
  6. front_end/
  7. inspector_overlay/
  8. node_modules/
  9. scripts/
  10. test/
  11. third_party/
  12. v8/
  13. .clang-format
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .mailmap
  22. .npmignore
  23. .npmrc
  24. .style.yapf
  25. .stylelintignore
  26. .stylelintrc.json
  27. AUTHORS
  28. BUILD.gn
  29. codereview.settings
  30. DEPS
  31. LICENSE
  32. OWNERS
  33. package-lock.json
  34. package.json
  35. PRESUBMIT.py
  36. README.md
  37. tsconfig.json
  38. WATCHLISTS
README.md

Chrome DevTools frontend

npm package

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

Source code

The frontend is available on chromium.googlesource.com.

Project documentation

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