Ensure we dispose of targets when they crash

I found this issue via the attached bug where the performance panel
would freeze. We tracked it down to this line of code:

```
await SDK.TargetManager.TargetManager.instance().resumeAllTargets();
```

Which would never complete, and the UI would never update.

Looking in the protocol monitor, we found that there was a
`Target.targetCrashed` event being emitted. Further investigation
confirmed that if a target crashed, and then you called
`resumeAllTargets`, it would never resume, because the crashed target
would not resume.

To fix this, we listen to the crashed event in the target manager and
dispose of the target when it crashes. This fixes the bug in the
performance panel, because now DevTools can move past the crashed target
and does not attempt to resume it.

Bug: 333989070
Change-Id: I7c128c321ff396ed8bc1c9347ab08e22b003f59c
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5458415
Reviewed-by: Simon Zünd <szuend@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
2 files changed
tree: 106c0667cecb38188c8b1bd456ae64386d50a95c
  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