Versions >152.0.6 crashes after running for a minute or so.

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

1. 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.
2. 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.)

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

I'm currently running 152.0.6 so not sure if these are what you need. I may have to install the current version first?

bp-47475217-b9c9-49df-a1dd-1f26d0260731 7/31/2026, 12:23 PM View bp-8ac7930b-09e8-4b26-920d-85c810260825 8/25/2026, 3:16 PM View bp-f9cd539b-a4ed-4029-ad0c-bb4ed0260825 8/25/2026, 3:17 PM

After reading the "Troubleshoot Firefox Crashes ..." article, I realize a better description of my problem is that Firefox "hangs". I guess it never crashes, but goes unresponsive and I have to kill it either with Ctrl-Alt-Del or Windows realizes it is unresponsive and brings up a pop-up that lets me close it.

These crashes are from 152.0.6 so are current for you, and are sort of "known unknowns" — one is a kill for data sanitization hanging at exit, two are graphics process crashes. But it sounds these are not the issues you'd like to diagnose, unless directly connected to your reported problems on 153 and above.

Have you tried running the later versions in Troubleshoot Mode first, if the behavior is the same?

If you don't want to upgrade your release again, you can experiment using the separate Firefox Nightly nightly.mozilla.org — it will come with a separate profile so you can poke at its performance and configuration separate from your day–to–day setup … to see if there's anything that seems to help, compared to your previous 153/154 experience.

So, I've been running Nightly most of the day and have not experienced any of the hangs that have been a problem with the release channel recent versions. After it ran OK for a while, I used Sync to load my bookmarks, etc. and still saw no problem. I guess that could mean that a bug has been fixed in Nightly that will eventually show up in Release?

I did try the Troubleshoot mode in one of the 153 versions and didn't help.

So, I'll try the current release channel version once in a while and hope the fix will show up before long.

Thanks for you speedy replies.

That's usually a good sign. It indeed usually means that if there was an issue, it's very possible it's something already fixed and just waiting to ship on the release channel some time later. (It can sometimes also mean there's a long–term experimental code that might not be yet ready for prime time, so it's gated for Nightly only, and that can also unintentionally resolve things, so it's not 100% chronological, but it's definitely a good result in itself.)

To put this into some perspective, if you were alright on 156 Nightly, chances are the current 156 Beta as available now would also yield the same results. That would be a good signal once 156 release is out in a few weeks, this could be resolved for you even on stable channel.

Out of curiosity, when 156 Nightly worked for you back then, does 156 Release available these days perform the same, or the issue persists?

Yeah, I've been running 156.0.1 since September 7, and have not seen the hang-ups (freezes) that happened with 152 etc. There have been a few true crashes, not hangs (Firefox asks to send a crash report which never happened with the 152 problems).

Good to hear, thanks!

Feel free to share the newer crash IDs after collecting a few, using the steps shared earlier, if there's anything to look into — there seemed to a be a couple pre–existing wrinkles, potentially just running out of resources, so it might be just that, as before.

Actually, I mis-read the version I had after Sept 7 - it actually was 155.0.1. Installed 156 on 9/27 and so far it is behaving similar to 155. The "crashes" I've seen have occurred as I close the program. I'll collect a few and send them later in case they help your development.

With both 155 and 156, have now seen a couple of "freezes" in which the spinning-wheel cursor persists until Windows pops up the unresponsive app window. But I've found that if I wait it eventually will un-freeze.

Thanks for your help and advice.

I do see in the older v152 logs that there's a shutdown hang on clearing data — there's an update on that front now in v157… and the older GPU process is something I've seen since v154 on W10 where browser and the graphics process can't talk to each other (possibly the graphics process hangs, and the browser then crashes when repeatedly waiting for it) — weird it was already on v152 for you, that looks like something on the system.

More interestingly, it's intriguing how the Nightly of the same version sounds like working just fine on the same system?

The crash on shutdown is not something I remember seeing until 155 and 156. And, not sure I'd put much weight on the 156 Nightly experience. I may not have used it long enough to see the problems I've seen now with 155 and 156. They are pretty infrequent.

I turned auto update back on this morning so will be running 157 after next restart.

Cheers.