Take a 'system snapshot' of your Mac when reporting a bug

When you tell a developer “my Mac was slow when I opened your app,” they have no way to know whether your CPU was at 100%, you were out of RAM, or your network was choked. A short system snapshot — a screenshot plus a few terminal outputs — turns a vague bug report into something actionable.

The five-minute snapshot

Here’s a quick template that covers the basics.

1. Activity Monitor screenshot

1. Open Activity Monitor.
2. Click CPU, sort by %CPU descending. Cmd-Shift-4 + space, click the window — screenshot.
3. Switch to Memory tab, sort by Memory. Screenshot.
4. Optionally Disk and Network tabs.

This shows whoever’s reading the report exactly which processes were doing what.

2. Terminal one-liners

uptime && sw_vers && sysctl -n hw.model

Tells the reader your macOS version, your Mac model, and how long it’s been running.

top -l 1 -o cpu -n 10 -stats command,cpu,mem,threads

A one-shot top sample of the top 10 CPU users.

vm_stat 1 5

Five seconds of virtual memory stats — useful for seeing if you were swapping.

iostat -w 1 -c 5 disk0

Five disk I/O samples.

3. powermetrics summary (for thermal/power issues)

sudo powermetrics —samplers cpu_power,smc,thermal -i 1000 -n 10 > ~/snapshot.txt

Ten seconds of CPU power, temperatures, and thermal pressure. Attach snapshot.txt to the report.

4. The Apple way: sysdiagnose

For deeper issues, especially ones Apple support is involved in:

sudo sysdiagnose -f ~/Desktop

This produces a large tarball (.tar.gz) with logs, configuration, and state — what Apple engineers ask for. It’s gigantic; only attach it when explicitly asked.

5. A clean menu-bar screenshot

If you have a menu-bar monitor running, the bar itself is a one-glance summary of system state. A screenshot of the bar at the moment of trouble is honestly often enough.

1. Install Beacon.
2. Enable CPU, Memory, Network, and Temperature in the bar.
3. When something goes wrong, take a screenshot of the menu bar (Cmd-Shift-4, drag a thin rectangle across the top).
4. Click any Beacon readout for the detail panel and screenshot that too — it shows recent history graphs as well as live numbers.

A small etiquette note

Strip anything sensitive before sending — Activity Monitor’s process list can include filenames, document titles, and other private context. A quick scroll through the screenshots before attaching them is worth the ten seconds.

The other rule: capture the snapshot while the bug is happening, not afterwards. Numbers thirty seconds after the moment of pain look totally different from numbers during.