Thrum

What is ReportMemoryException, and why is it running?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

ReportMemoryException is a macOS service that generates memory usage diagnostic logs when system events call for them, such as a process going over its memory limit. When it runs, some process has just used more memory than allowed. The process to investigate is the one the report names, not ReportMemoryException.

ReportMemoryException at a glance

ReportMemoryException
Made byApple (part of macOS, diagnostics)
TypeSystem daemon
Location/usr/libexec/ReportMemoryException
Runs as_reportmemoryexception (a system account)
Started bylaunchd job com.apple.ReportMemoryException
Can you quit it?Not usefully. launchd starts it again at the next memory event.

What is ReportMemoryException?

The ReportMemoryException(8) man page says it is a system service which should only be launched by launchd, and that it generates memory usage diagnostic logs as indicated by system events such as memory limit violations.

It runs as its own system account, _reportmemoryexception, through the launchd job com.apple.ReportMemoryException, which starts it on demand. On the Mac checked here it had not run since startup.

Is ReportMemoryException safe?

Yes. It is part of macOS at /usr/libexec/ReportMemoryException and is signed by Apple.

Why does ReportMemoryException use so much memory and CPU?

How much memory is normal for ReportMemoryException?

Typical: not running. A run now and then means a process hit a memory limit once.

Frequent runs mean one process keeps using too much memory.

How do you find the process that used too much memory?

  1. Check memory in Activity Monitor. Open the Memory tab and sort by Memory. A process whose memory keeps climbing is the likely cause.
  2. Look at diagnostic reports. Open Console and look through the reports in its sidebar, or check /Library/Logs/DiagnosticReports in Finder. Report file names include the process name.
  3. Quit or update the app. Quit the process named in the reports and update it. A process that keeps growing may have a memory leak.

When should you worry about ReportMemoryException?

Frequent reports for the same process point to a leak in that software. ReportMemoryException is only the messenger.

A copy outside /usr/libexec would not be Apple's.

How do you check ReportMemoryException in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type ReportMemoryException in the search field. The Memory tab shows its Memory. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every ReportMemoryException process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'ReportMemoryException' | grep -v grep

How can Thrum help with ReportMemoryException?

Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much ReportMemoryException holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

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 about ReportMemoryException

Does ReportMemoryException mean my Mac is out of memory?

Not necessarily. It reacts to events such as one process going over its own memory limit. Check Memory Pressure in Activity Monitor for the whole Mac.

Can I turn it off?

No. It is part of macOS and runs only when such events happen.

Sources