5 guides

Memory pressure & leaks

A large memory number is only the beginning. Use memory pressure, app behavior, and changes over time to decide what deserves investigation.

Start here

  1. Check whether memory is the bottleneck

    Start with the Memory Pressure graph, compression, and swap. Distinguish overall demand from a single process that keeps growing.

    Read the guide →
  2. A browser helper is using the memory

    Trace Chrome helpers to tabs or extensions with the browser’s task manager, then check whether the load returns after a restart.

    Read the guide →
  3. One process grows after repeated actions

    Record the pattern and reproduce it. Use the memory-leak guide when you need to move from finding a process to deeper profiling.

    Read the guide →

Suggested reading

Work through the guides that match your situation, in the order below.

Tools for your investigation

Start with Activity Monitor

Use Apple’s built-in tool for an initial check. Its official guide explains the available views and measurements.

Read the guide ↗

Go deeper with ProcXray

Inspect the process tree, resource history, and process details together. Start with the product overview or follow the setup guide.

Explore another topic