Why is Firefox using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
Firefox runs the browser in one process and web pages in many others: isolated processes for individual sites, plus processes for extensions, the GPU and media decoding. In Activity Monitor most of them appear as plugin-container. Firefox's Task Manager (Tools > Browser Tools > Task Manager, or about:processes) names the tab or extension behind each process and lets you close or unload it.
What are the Firefox processes in Activity Monitor?
The Firefox app bundle contains the main firefox executable and separate helpers. On a Mac you see:
- firefox: the parent process that draws the browser window and launches every other process.
- plugin-container: the child processes. Firefox uses them for web content (one pool per site with site isolation, called Fission), extensions, about: pages, local files, network and utility work.
- Firefox GPU Helper: compositing and drawing with the graphics processor.
- Firefox Media Plugin Helper: started only for DRM-protected video, to run the decryption module in a sandbox.
Because the content processes all share the name plugin-container, Activity Monitor alone cannot tell you which site is busy.
How do you see which tab or extension is using CPU in Firefox?
- Open the Task Manager. Choose Tools > Browser Tools > Task Manager, or type
about:processesin the address bar. - Sort by CPU or Memory. Click the CPU or Memory column. Each row is labeled with the site (for isolated web processes), Extensions, GPU, Network, Utility and so on, with its process ID in brackets.
- Close the tab or unload the process. Use the row's action button: Close tab for a single tab, or Unload tabs and kill process to stop a whole content process. You can reload the tabs afterwards.
- Check extensions. If the Extensions row is busy, choose Tools > Extensions and Themes (or type
about:addons) and turn extensions off one at a time. - Profile a stubborn process. The Task Manager can profile all threads of a process for a few seconds, which records what the code was doing. This is useful when you report a problem to Mozilla or a site owner.
Why does Firefox use so much memory?
Site isolation keeps each site's data in its own process, which protects you from malicious pages but costs memory for each additional process. Firefox also keeps a preallocated content process ready so new tabs open quickly.
Firefox > Settings > General > Performance has a Use recommended performance settings checkbox. When you clear it, Firefox shows Use hardware acceleration when available and, where multiprocess Firefox allows, a Content process limit. Firefox's own description notes that more content processes can improve performance with many tabs but use more memory.
When is Firefox's CPU use not normal?
- A single site row in about:processes stays near 100% CPU with the tab in the background. A script on that page is looping; close or unload it.
- The Extensions row uses CPU on every page. One extension is doing heavy work; disable them one at a time to find it.
- Firefox GPU Helper stays busy with no video playing. Try clearing Use hardware acceleration when available, restart Firefox and compare.
- Firefox uses CPU after you quit it. Check Activity Monitor for leftover plugin-container or firefox rows and quit them there.
How can Thrum help with Firefox?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when Firefox is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click Firefox in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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
What is plugin-container on a Mac?
It is the executable Firefox uses for its child processes: web content, extensions and utility work. Despite the name, it no longer means browser plug-ins such as Flash.
Is about:processes the same as about:memory?
No. about:processes is the live Task Manager with CPU and memory per process. about:memory produces detailed memory reports and is mostly useful when reporting a bug.
Sources
- Firefox Source Docs: Process Model
- Menu, Task Manager and Settings wording checked in Firefox 157.0 for Mac (menubar.ftl, aboutProcesses.ftl, preferences.ftl)