The new version of FF only crashes!!!!!!!!!!

Hi Hashachar70,

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.

Thank you for replying.

I did as you suggested, and I get a black screen which states "No crash reports have been submitted." Something I noticed every time my FF crashed was that there was only notification to Microsoft about the crashes, and nothing to FF.

I know I can't be the only person this is happening to, as I've seen others posting the same problem.

Then try to see if others' posts include any crash logs that can be used to check for any trends, and share the links to these threads here. Thanks.

It seems everyone else is having the exact same experience, there are no crash logs for our crashes.

I haven't seen other crash report from 154 so far, but I'll keep looking. Can you confirm how did you install Firefox? Was it from the MS Store or you installed it from the .exe file?

I've been running Firefox for yrs and the issue of repeated tab crashes is extremely problematic and a RECENT phenomenon. I'm running v154.0 on a windows 11 machine w/all updates. Maintenance finds no issues yet Firefox repeatedly crashes tabs on attempts to open and also just to open Firefox as well. As a note there are over 40 (FORTY) tab crashes in under 20 minutes just this morning, in fact this tab crashes mid-message and had to be restored:

bp-37bf1245-5f91-439c-9b49-3b4dc0260819 8/19/2026, 9:52 AM View bp-ea6250ec-0787-4f7f-becd-319720260819 8/19/2026, 9:52 AM View bp-90f00eca-c5a0-42d2-ba23-87f6e0260819 8/19/2026, 9:52 AM View bp-674ba0ba-5e42-47b5-8c9f-c40580260819 8/19/2026, 9:52 AM View bp-9c7293a7-99a2-4a47-86ff-f3d370260819 8/19/2026, 9:52 AM

Hi, Kiki.

I don't know where you were looking for examples, so here are 14: https://support.mozilla.org/en-US/questions/firefox#search

I only use Mozilla, never MS.

It doesn't seem to be crashing anymore (hopefully because it is fixed, and this isn't just a pause on crashing), HOWEVER, when I click on "clear browsing data" (as I do after every time I leave a site) in my Settings > Privacy and Security in my FF browser, I now get long glitches in erasing the browsing data. IE, it takes up to 2 minutes to complete a small amount of data deletion. I wonder if this has something to do with the update? ~Beth

here's a few more crash reports: bp-a8fbdd16-f4ec-40c1-a23f-92c610260819 8/19/2026, 10:17 AM View bp-70d0a698-07db-4901-876d-8461d0260819 8/19/2026, 10:14 AM View bp-a4645cd7-5039-4aee-bd07-2a1510260819 8/19/2026, 10:14 AM View bp-655261e2-ef07-4592-955b-a06020260819 8/19/2026, 10:14 AM View bp-c063d3c4-78f0-4f30-a0f7-cfa310260819 8/19/2026, 10:14 AM View bp-8283761b-e566-446e-8abc-18a470260819 8/19/2026, 10:14 AM View bp-b7dde2d8-7587-4b3e-8b57-d537b0260819 8/19/2026, 10:14 AM View bp-7d5557ab-520a-41fa-8dc9-a48a50260819 8/19/2026, 10:13 AM View bp-3c0e74f9-a5b1-4101-ac69-447cc0260819 8/19/2026, 10:00 AM

cannot open any sites at this point. washingtonpostDOTcom, bostonglobeDOTcom don't just crash the tab but crashes Firefox and must restore the session

The above is constant out–of–memory while the system has plenty of resources. Did you try restarting into Troubleshoot Mode (from Help menu) or running a separate Profile to test, to eliminate any customizations? Basically your system has the resources, but when allocated, the OS doesn't provide them:(

(Realistically there's some statistically bizarre signatures in those reports above, that I'd suggest running a hardware test, something like a good RAM fault check, to eliminate e.g. a bad memory module.)

jbr:

This problem began for (I'd assume) thousands of people immediately after the latest update.

The crash report is only sent to Microsoft and not recorded at all by FF, so it looks like nothing has happened.

This is not due to anything else, just the latest FF update.

Can someone please just take this seriously and address it?

Yes, I have Win 11, Lenovo Yoga 7 2 in 1 laptop. I run FF and only FF browser.

I update everything on my laptop immediately upon turning it on in the morning, before doing anything else.

Beth, can you please share any link with the reports? Your thread is the only one for v154: support.mozilla.org/en-US/questions/firefox?show=all&tagged=firefox-1540%2Capp-crash

jbr:

You are communicating with 2 different people.

I shared 14 links, above.

Unfortunately that is one single link to search interface, with no results, no time or version range. Can you at least share a picture of what are the thread names you see?

Now I understand what you are saying.

I saw all those other subject lines and assumed they were about the latest change, although other people stated that they had the same exact problem, with crashing after an update and FF not making any kind of record of the crashes, so maybe it is the same thing going on as beforehand?

After going thru Troubleshooter Mode - found nada and the crashes persisted as well as a system re-boot I got fed up w/Firefox and UNINSTALLED and then re-installed. It seems if you do a re-install that the tab crashes go away - at least, for me, currently, tomorrow is another day LOL

Oh, no, that was an update issue in v153 a month ago that yes didn't get caught by the crash reporter as the update failed in a very bad way (presumably over files still being open, locked by the system, or restarted during the update) and the only recovery at that state was to simply download the installer from firefox.com and run it again to sort out the mismatch manually.

I mean, you can also try the same — it doesn't hurt to run the full installer, it's just not the same cause as last month, which has a shim added to always step over that issue and start anyway, to enable further updates normally.

Can you describe the scenario a bit more? I see this question posted from v154 that is apparently stable enough to open this site — is that on another device, or the startup failure is not persistent, or it only affects one single profile — or something specific like this?