tracing: Disallow trace events during TLS teardown

Don't attempt to write trace events when TLS data for a thread is being
deallocated. Otherwise this may lead into unexpected re-entrancy.

An example scenario from Chrome:

1. ~TracingTLS causes an active trace writer to be destroyed.
2. The trace writer posts a task to return chunks to the service.
3. While the task is being posted, the task runner support code in
   Chrome hits a trace event, which creates a new trace writer.
4. The trace writer creation causes another task to be posted, causing a
   crash due to task runner re-entrancy.

Bug: 180295966
Change-Id: Id8c473520b88b62e11812beb80a076699a6df244
1 file changed
tree: 6decdeebc0395084b6500432c99a54ff7de0406d
  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. DIR_METADATA
  30. heapprofd.rc
  31. LICENSE
  32. meson.build
  33. METADATA
  34. MODULE_LICENSE_APACHE2
  35. OWNERS
  36. perfetto.rc
  37. PerfettoIntegrationTests.xml
  38. PRESUBMIT.py
  39. README.chromium
  40. README.md
  41. TEST_MAPPING
  42. traced_perf.rc
  43. 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.