janestreet/magic-trace

magic-trace collects and displays high-resolution traces of what a process is doing

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 10th, 2026
Created on January 26th, 2022
Open Issues & Pull Requests: 70 (+0)
GitHub issues: Enabled
Number of forks: 209
Total Stargazers: 6,267 (+0)
Total Subscribers: 41 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.9 days
Mean response time: 286.8 days
90th percentile: 1451.8 days
Tracked items: 24

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 993 days
Stale 30+ days: 14
Stale 90+ days: 12

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (21)
  • enhancement (5)
  • good first issue (4)
  • ui (1)

Most active issues this week

Detailed Description

magic-trace is a performance profiling and tracing tool that collects and displays high-resolution traces of process execution on x86 systems.

The tool addresses the need to understand fine-grained process behavior during execution. It works by capturing detailed traces of what a running process is doing and presenting this information in a visual format that developers can analyze. This approach enables inspection of process activity at a level of detail that standard profilers may not provide, making it useful for performance investigation and debugging scenarios where understanding exact execution flow matters.

The tool is suited for developers working on performance-critical systems who need to inspect process behavior in detail. It targets x86 platforms specifically. Anyone considering adoption should understand that magic-trace is designed for deep introspection of process execution rather than high-level profiling summaries, making it most valuable when you need to see what a process is actually doing at a granular level rather than aggregate statistics about where time is spent.

The project shows active development with regular commits across multiple areas of the codebase. Pull requests are reviewed and merged consistently, indicating ongoing maintenance and responsiveness to contributions. The maintainers have established a dedicated project website separate from the repository, suggesting investment in documentation and user-facing presentation of the tool.