Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe
Rezolvat

Pages keep crashing and need to be reloaded, especially tabs.

mdupuy500

Some pages keep crashing and need to be restored. Even if I open new tabs, once I get to them most of the time they have crashed and need to reloaded too. Even after reloading they will continue to crash. This after Firefox's latest update.

Some pages keep crashing and need to be restored. Even if I open new tabs, once I get to them most of the time they have crashed and need to reloaded too. Even after reloading they will continue to crash. This after Firefox's latest update.
Capturi de ecran atașate
Citește răspunsul în context

Soluție aleasă

No no, the screen shot you uploaded is indeed a content process crash, or a "tab crash" — which generates the same crash reports like parent app crashes, for investigation.

What is weird is none are being created:/

Funnily enough I'm getting these (semi–)deliberately now on a Mac from a botched update, and, to my surprise these also do not appear to be logged in the crash stats. So maybe it's botched beyond even being capable assembling the crash reports?

Could you please try downloading a new installer from firefox.com and just drag the app over your existing one to iron out any potential wrinkles? Thanks!

Toate răspunsurile (4)

This might in theory be a badly applied update — could you please check if the crashes got submitted, and a paste a few here to see what's going on? Thanks:

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

Fx115aboutcrashes

Thank you for your help!

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

@jbr, I have no crash reports, submitted or not, none appear as per your instructions. Maybe I shouldn't have used the word crash, but more as it appears in the photo I uploaded.

Soluție aleasă

No no, the screen shot you uploaded is indeed a content process crash, or a "tab crash" — which generates the same crash reports like parent app crashes, for investigation.

What is weird is none are being created:/

Funnily enough I'm getting these (semi–)deliberately now on a Mac from a botched update, and, to my surprise these also do not appear to be logged in the crash stats. So maybe it's botched beyond even being capable assembling the crash reports?

Could you please try downloading a new installer from firefox.com and just drag the app over your existing one to iron out any potential wrinkles? Thanks!

jbr, installed it again. Seems to be fixed, at least in small test run of sites I know would crash. If you don't here from me again, after using it for a while longer, then the issue is permanently fixed. Thanks so much for your attention and help.

Adresează o întrebare

Trebuie să intri în cont ca să răspunzi la o postare. Te rugăm să adresezi o întrebare nouă dacă nu ai încă un cont.