Find out what kept your Mac busy.

When the fans spin up or the battery drains faster than it should, CrashPulse has already noted which app did it, for how long and how hard. It lives in the menu bar and keeps watch while you work.

See what it does Version 0.1.0 beta, for macOS 14 or later on Apple silicon and Intel Macs.
Busy in the background

Indexer kept the CPU at up to 254% for 4m 10s while you were using other apps.

Example event

What CrashPulse shows you

Screenshots show CrashPulse with example data.

Every long CPU spike, kept

CrashPulse checks your Mac every few seconds. When an app keeps the processor busy for 30 seconds or more, it records an event with when it started, how long it lasted and how high it went.

Events are grouped by day, so you can look back at the fan noise from this morning or the battery drain from yesterday. An app that keeps doing it in the background on separate days gets called out at the top.

The CrashPulse menu bar panel listing CPU events grouped by day, each with a small CPU trace and its peak.
The event list, with example data.

A plain answer about who did it

Open an event to see the app most likely responsible and how serious it was. CrashPulse tells you whether it happened while you were using that app or while it worked in the background.

One CPU trace runs from before the event to after it, next to the duration, the peak and an estimate of the CPU energy it used. Below that is a short suggestion for what to do, and the processes that took part.

An event detail: the app name, a sentence saying it kept the CPU at up to 170% while other apps were in use, a CPU trace, three figures and the processes involved.
An event that is still happening, with example data.

What is using the processor right now

Live ranks apps by CPU use or by CPU power, with a trend for the last three minutes. Helper processes count toward the app they belong to, so a browser and its dozen helpers appear as one row.

Expand an app to see its processes, or open the full list to search by name or process ID.

The Live view: total CPU over the last three minutes and the top apps ranked by CPU power, each with a share bar, CPU percentage and power in watts.
Live, with example data.

How it measures

Sustained, not momentary
Short bursts are normal. An event needs 30 seconds of continuous load from one app or process, so opening a big file does not count.
Apps, not just processes
Background helpers are added up under the app that owns them. Load spread across several helpers still adds up to an event.
Fair to busy Macs
The trigger adapts to how busy your Mac usually is, so a machine that always runs a heavy workload is not flagged all day.
CPU energy on Apple silicon
Where macOS reports it, CrashPulse estimates the CPU energy an app used. Graphics, the display and charging are not part of that figure.
Stays on your Mac
History is kept on your Mac for seven days. There is no account, nothing is uploaded, and no special permissions are needed.
Never interferes
CrashPulse does not quit, slow down or change any app. It tells you what happened, and you decide what to do.

Some processes that belong to macOS itself cannot be read by ordinary apps, so their spikes may not appear. CrashPulse names the most likely contributor based on what it can measure.

System requirements

macOS
macOS 14 Sonoma or later
Mac
Apple silicon or Intel. One universal app runs natively on both.
CPU energy estimates
Apple silicon. Intel Macs show CPU use without energy.
Permissions
None. CrashPulse does not ask for Accessibility, Full Disk Access or screen recording.
Security
Signed with an Apple Developer ID and notarized by Apple.
Installer
A disk image of about 2 MB
Current release
0.1.0 beta

Install

  1. Open the CrashPulse disk image.

  2. Drag CrashPulse onto the Applications folder in the window that opens.

  3. Open CrashPulse from Applications.

    A short welcome explains what it watches. CrashPulse has no Dock icon.

  4. Click the waveform icon in the menu bar to see events and live use.

    Monitoring starts on its own. The first readings appear after a few seconds.

To remove CrashPulse, choose Quit in its panel and move the app to the Trash. Its history is in ~/Library/Application Support/CrashPulse and can be deleted too.

Availability

Not on sale yet

The current release is CrashPulse 0.1.0 beta, signed and notarized by Apple. Pricing and a way to buy will appear here when sales open.