How do you find an app with a memory leak on a Mac?
Last reviewed: 19 November 2026.
Note each app's value in Activity Monitor's Memory tab, then check again after an hour or two of normal use: an app whose Memory keeps rising while you are not giving it more work is the likely leak. Quitting and reopening it gets the memory back until the developer fixes it.
How do you spot a leak?
- Take a first reading. Open Activity Monitor, click Memory, choose View > All Processes and sort by Memory. Note the values of the top ten.
- Use the Mac normally. Leave the same apps and documents open. Work as usual for an hour or more.
- Compare. Sort by Memory again. Growth that matches what you did (a large file opened, many tabs) is expected. Steady growth in an app you left alone is not.
- Watch one process closely. Double-click it to see Real Memory Size and Private Memory Size, or log it in Terminal as shown below.
- Confirm and work around. Quit and reopen the app. If memory falls back and then climbs again in the same way, report it to the developer with the version number.
How do you log one app's memory over time?
footprint --sample 60 Safari
while true; do date '+%H:%M'; top -l 1 -pid 1234 -stats pid,command,mem | tail -n 1; sleep 300; done
footprint --sample 60 prints the app's footprint every 60 seconds with a timestamp, broken down into categories such as MALLOC; use a PID for helpers that share a name. The loop prints the time and top's MEM figure for PID 1234 every five minutes. Stop either with Control-C. For processes you do not own, footprint needs sudo.
Is it a leak or a cache?
Many apps keep data in memory on purpose: browsers keep recent pages, photo apps keep thumbnails, and mail apps keep message lists. That memory grows quickly and then levels off. A leak keeps growing with no ceiling. Also check the Compressed Memory column: leaked memory that is never touched again tends to be compressed or swapped, so a leaking app often shows a large and rising compressed figure.
The Memory Pressure graph tells you whether it matters. A slow leak in an app you restart daily may never turn pressure yellow.
What do developers use to confirm a leak?
leaks searches a process's memory for blocks nothing points to any more and prints them; run leaks 1234 on a process you own. With the MallocStackLogging environment variable set when the app started, it also shows where each leaked block was allocated. vmmap -summary 1234 shows how the process's memory is split between regions. Xcode's Memory Graph Debugger and Instruments give the same information graphically.
How can Thrum help?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory. An optional alert tells you when memory pressure turns critical.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
Can macOS itself leak memory?
System processes can, and a restart clears it. If a system process such as WindowServer grows to many gigabytes, note the macOS version and the apps you used and report it to Apple with Feedback Assistant.
Does a memory leak damage the Mac?
No. It wastes memory until the app quits. The worst effect is a slow Mac from swapping.
Sources
- footprint(1), leaks(1) and vmmap(1) man pages: run man footprint, man leaks and man vmmap in Terminal
- Activity Monitor User Guide: View memory usage