Abort traces if duration_ms is too high to prevent overflow bugs

Prior to this change the guardrail for too-long traces was
triggered only for non-interactive traces.
However, turns out that if the duration_ms is accidentally too
high (e.g. 0xffffffff) that triggers subtle overflow bugs in the
watchdog logic of the traced_probes process.
This CL caps also the duration of the non-interactive traces.

Test: perfetto_unittests
Bug: 73051872
Change-Id: I76dbe5cfaf59c22e72d203da05c51d6200bd2ef0
2 files changed
tree: 72122bb29df742ea7d5cadd77a0da7cf3171e23f
  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
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.