// Managing and querying Perfetto traces using the trace_processor MCP server.
Key commands for building, debugging, and testing in V8. Use when needing command syntax for gm.py, d8 flags, or run-tests.py. Do not use for environment setup.
Workflow for performance and memory evaluation in V8. Use when tasked with improving the performance or memory usage of a workload in V8. Do not use when debugging a crash or functionality issue.
Workflow for evaluating and refining agent debugging capabilities using designated test cases and Swarm principles. Use when evaluating subagent performance or creating benchmarks. Do not use for regular bug fixing.
Workflow for issue-based debugging in V8. Use when tasked with debugging a specific issue, usually associated with a Buganizer ID or a specific reproduction script. Do not use for performance regressions.
Guides the initial analysis and impact assessment of a V8 security report, strictly excluding implementation or fixing.
Checks if a POC provided by some JS and d8 flags is a vulnerability or just a regular bug.
| name | trace_processor |
| description | Managing and querying Perfetto traces using the trace_processor MCP server. |
The trace_processor extension launches a long-running FastMCP server wrapping
Perfetto's trace processor capabilities, allowing seamless interaction with
trace files (.pftrace, .perfetto-trace, .pb).
For comprehensive guidance on querying traces, utilizing standard library
modules, and schema structures, refer directly to the native Perfetto AI skills
inside third_party/perfetto/ai/skills:
slice,
thread, process, sched_slice, and track.slices.with_context by starting queries with INCLUDE PERFETTO MODULE.