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.
All Replies (3)
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
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.