After upgrading to version 152.0, Firefox now grabs up memory and freezes.
Dear Support Person,
Yesterday, after being notified that an upgrade was available, I executed the upgrade to version 152.0.
The upgrade completed successfully with my eight tabs populating on the left side along with a new tab showing all the features of the new upgrade.
I opened my Gmail tab and my Yahoo mail tab. Eventually, Firefox froze up, saying it was Not Responding. I looked at Task Manager and saw that Firefox was continuing to grab up memory. I ended the Firefox process in Task Manager.
I then opened it again and deleted all the tabs except for one. It continued to grab up memory.
I then opened it in Troubleshooting mode. It errored out, and I sent the report to Firefox support.
The only thing that has changed is the fact that I ran the upgrade to Firefox. Nothing else has changed.
Firefox has been my go-to browser for years. I am using Chrome as my access to the internet now, and cringe every time I go into it.
I hope and pray that you can bring my Firefox friend back to me.
I am anxiously looking forward to hearing from you.
Take care and God bless!
~ Kyle P.S. I just tried getting information from about:support. I was able to copy the raw data and then the application crashed. I sent the Crash Report to you folks. The raw data I pasted in the Troubleshooting Information box.
Valgt løsning
These recent two are enough, thanks. There's nothing to worry about, you're not affected by the CPU degradation I mentioned earlier, that's unrelated in your case. There's nothing particular in these logs, they just ended up hanging — might have been a brief period of bad interaction with your security software, or some of the sites adjusting to the new browser session ending up with e.g. connections hanging or a backlog of polling things that affected the performance at the time. If that's settled down there's nothing to worry about at this point.
Alle svar (7)
Folks,
This is Soaring8Eagle, the one who posted the problem.
Well, after the latest opening of Firefox with its "standby updating" message, it appears to be working. The version now is 152.0.1, not 152.0.
With 8 tabs open, the memory usage per Task Manager bounces around between 2,521 and 2,555 MB. Before it was constantly climbing until it froze.
Now, per Task Manager, Firefox has 26 (sessions/threads). Is that normal? And compared to Chrome, Firefox uses a lot more memory. Any comments on that insight would be appreciated.
I have a pdf file of the text of the Troubleshooting Information. I just don't know how to get it to you.
Anyway, this has been a journey for me. Any thoughts or insights you might be able to add to this adventure will be appreciated.
Take care, and every blessing to you!
~ Kyle P.S.: Just in the time that I have been creating this message, the memory usage has dropped down to around 1860 MB. I'm assuming that's a good thing, but am scratching my head to understand why...
Hey Kyle, chances are you're affected by this CPU bug:
If you have crash reports collected, once they are submitted I can verify that for you:
- Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) Crash Reports will appear, similar to the one shown below.
- Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Hey, jbr,
Thanks so much for getting back to me so quickly.
Below are the two Submitted Crash Reports from yesterday and today and the remaining 3 are from 2017 and 2015. There are also 6 more (the newest from 2015 and the oldest from 2012). Do you need those report IDs also?
There are also 4 Unsubmitted Crash Reports (3 from 2023 and 1 from 2022). Should I submit those?
Thanks again, jbr. I look forward to hearing from you.
~ Kyle
Submitted Crash Reports Report ID Date Submitted bp-c6f2c139-a669-466c-a401-f7e0e0260618 6/18/2026, 2:24 PM bp-0b2325e5-30b2-48fd-add9-1d9c70260617 6/17/2026, 4:16 PM bp-23d694c9-05ed-4eb8-83bb-5beac1171113 11/13/2017, 10:35 AM bp-7e1cd3ae-80e7-44e0-8f06-b514e1170807 8/7/2017, 3:42 PM bp-38f17fd9-6ac5-4b5a-9a60-828712150916 9/16/2015, 8:47 AM
Valgt løsning
These recent two are enough, thanks. There's nothing to worry about, you're not affected by the CPU degradation I mentioned earlier, that's unrelated in your case. There's nothing particular in these logs, they just ended up hanging — might have been a brief period of bad interaction with your security software, or some of the sites adjusting to the new browser session ending up with e.g. connections hanging or a backlog of polling things that affected the performance at the time. If that's settled down there's nothing to worry about at this point.
Dear jbr, thank you for taking the time to do the research and assure me that all is well, and there is no need to worry. That IS a relief!
I do have a few questions I was hoping you might address. However, if it is not appropriate in this forum, just let me know. I'll totally understand.
1. This all started after doing the upgrade to 152.0. Firefox would start consuming memory until it froze. The next day, after Firefox did a startup upgrade to 152.0.1, the continuous memory consumption stopped. Did the new version correct the continuous memory consumption issue?
2. Firefox: 11 tabs open. Task Manager shows memory usage around 2500 MB and 28 sessions/threads.
Chrome: 12 tabs open. Memory usage around 700 MB and 34 sessions/threads.
jbr, can you help me understand why Firefox uses so much more memory?
No matter what, jbr, please know that you are deeply appreciated. You are a blessing to those of us who love Firefox and all that it has been for us over the years. I am deeply grateful for your concern and dedication to supporting our portal to the internet world.
God love ya, my friend!!
~ Kyle
Oh I don't know enough about the low–level internals that impact things like individual processes and their resource consumption to be of any help here — I can only infer from the business side of things, and that's most people compare the perceived performance on surfaces owned by the other browser makers 😇 … which, realistically, are written to optimize on their rendering engines, and ideally leave the competitors' tech struggling to interoperate;) So to have a reasonable sample, you'd have to avoid any Youtube, G Docs, Gmail, Outlook, Office360 and similar sites, and just open a handful of, say, wikipedia pages — some with diagrams, some with long scrolling or tables, some with large media, some playing audio or video from their wikimedia sources using open codecs etc. … and compare such usage, that's neutral in relation to the browser maker and spared of any attempts to optimize for one engine, at the expense of the rest.
Hey, jbr,
Thanks again for your dedication and willingness to be of service to the folks who daily depend on this wonderful application.
Every blessing to you, jbr!
~ Kyle
Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.