ui: Refactor per-thread track creation

Remove a large amount track creation logic from the awful
process/thread loop. Instead we now hand many methods
which create tracks based on the track tables in the trace
processor and we only use the loop to create & sort track groups.
Behaviour wise this should be a no-op.

Long term we should:
- Remove the loop completely and group/sort tracks after the fact
- Move from a 'push' based model (for each track kind the UI knows
  about we have method to query the TP) to a 'pull' based model
  (we iterate over the tracks in trace processor and create the most
  appropriate kind of track from those we have available).

Change-Id: I66c9912149a521ad4b1b369a13c72b7916a5b533
1 file changed
tree: 65510f5f9c733ee1cccc38565d92b1de6569fda1
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. src/
  13. test/
  14. tools/
  15. ui/
  16. .clang-format
  17. .clang-tidy
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .style.yapf
  22. Android.bp
  23. Android.bp.extras
  24. BUILD
  25. BUILD.extras
  26. BUILD.gn
  27. CHANGELOG
  28. codereview.settings
  29. heapprofd.rc
  30. LICENSE
  31. METADATA
  32. MODULE_LICENSE_APACHE2
  33. OWNERS
  34. perfetto.rc
  35. PRESUBMIT.py
  36. README.chromium
  37. README.md
  38. TEST_MAPPING
  39. traced_perf.rc
  40. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.