trace_processor: fix bugs with Chrome scoped slices

This fixes 2 bugs:
1. An pre-existing bug which got more prominent after aosp/835064 to
do with scoped slices being closed too early even though child slices may have
been added to them subsequently.
2. Parent stack id being wrong because the wrong stack id was looked at

Change-Id: I810f0b03c4baa26e748b9fd0f55748e71ea8d95e
2 files changed
tree: 560932b75bfaef34a0ad9e9a3dacba39d734d93e
  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.