If Firefox is using an unexpected amount of RAM, report a bug by following the steps below:

1. Open about:memory in a new tab.
2. Click Measure and save…
3. Attach the memory report to a new bug
4. Paste your about:support info (Click Copy text to clipboard) to your bug.

If you are experiencing a bug, the best way to ensure that something can be done about your bug is to report it in Bugzilla. This might seem a little bit intimidating for somebody who is new to bug reporting, but Mozillians are really nice!

If you prefer not to open a bug, you can instead reduce the number of content processes used by Firefox to a lower amount by going to about:config and changing dom.ipc.processCount.webIsolated to a lower number.

@[email protected] The amount of RAM Firefox consumes depends on several factors. It could be due to a misbehaving browser extension, a website issue (I remember Firefox eating a lot of memory when I stay on YouTube for too long, with that browser tab taking up around 8GB, and I only noticed it because my system warned me about low memory, even though I have 32GB of RAM), or the number of tabs you have open.

If you encounter this issue (when it uses 10GB of RAM), try opening a new tab and enter “about:memory” in the URL bar. Then click on “Show memory details” to get a comprehensive breakdown of each process and its RAM consumption. If you prefer a simpler view, you can use “about:processes” instead of “about:memory.”

Is it a good idea to run Firefox for Android on my laptop instead of running Firefox for Windows?

Some things in addition to the above can also consume lots of RAM:

1. If you are not using an ad blocker, some code used by some ad companies are so memory intensive that they eat lots of RAM rather quickly. The easiest fix for those is to run an ad blocker. (I personally use uBlock Origin with mostly just the default settings.)

2. Leaving Firefox open for several days can eventually eat a good chunk of RAM. If practical, it is suggested to close and restart Firefox every day. (I start up Firefox at the start of my day and shut it down at the end of the day.)

3. If the GPU driver isn’t compatible with Firefox, “hardware acceleration” could both slow down Firefox (from crashing the thread trying to use the GPU) and end up grabbing a lot of memory in the process. The suggested fixes are, first, try to get the most recent supported graphics driver from the graphics chip manufacturer, and if that doesn’t take care of it, turn off “hardware acceleration” (in Menu -> Settings -> “General” page -> uncheck “Use recommended performance settings” and then you can see and uncheck “Use hardware acceleration when available”).