heapprofd: start task duration watchdog (default of 30s)

Tested manually. Automated testing would require a small refactoring that I
don't want to be part of this cl.

Note that the watchdog will start a thread that's useless for heapprofd (since
we're not doing cpu/mem limit tracking). WDYT, worth adding a TODO to add a
lighter-weight watchdog setup?

Change-Id: I1a17ff0149d7a30d1fd5300da3debd979aed0d53
1 file changed
tree: a349b42a8833785cdf20ee14784d1e24bdb439ca
  1. build_overrides/
  2. buildtools/
  3. debian/
  4. docs/
  5. gn/
  6. include/
  7. infra/
  8. protos/
  9. src/
  10. test/
  11. tools/
  12. ui/
  13. .clang-format
  14. .gitignore
  15. .gn
  16. .travis.yml
  17. Android.bp
  18. Android.bp.extras
  19. BUILD.gn
  20. codereview.settings
  21. heapprofd.rc
  22. MODULE_LICENSE_APACHE2
  23. NOTICE
  24. OWNERS
  25. perfetto.rc
  26. PRESUBMIT.py
  27. README.chromium
  28. README.md
  29. TEST_MAPPING
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.