Mozilla Relay is experiencing issues with call and text delivery. We’re working on a fix. Check Mozilla Status for updates.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Firefox crashes

  • 4 antwurd
  • 1 hat dit probleem
  • 16 werjeftes
  • Lêste antwurd fan Shadow110

more options

Firefox started without any of the previous session tabs as it was configured to. New tabs immediately crashed.

Firefox started without any of the previous session tabs as it was configured to. New tabs immediately crashed.
Keppele skermôfbyldingen

Alle antwurden (4)

more options

Hi, Video Card Drivers are a mess, if can update or reinstall would be great.

Please include the bp- and only need 5 :

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 Submitted Crash Reports list will appear, similar to the one shown below.
  2. Copy the 5 most recent 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.)

aboutcrashesFx57

Thank you for your help!

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

more options

If it is only tabs crashing then do not do the above.

more options

Whops sorry. Here are the crash ids.

Unsubmitted Crash Reports Report ID Date Crashed 484c1e52-f050-fc73-b30e-a67d7eb91d2b 7/5/18 10:07 AM 772659b9-84ac-cdb7-c915-3f0818c83321 7/5/18 10:07 AM 15f61ca5-7d57-b9e2-9ef4-145392a36a22 7/5/18 10:06 AM 77f8b910-d40c-1e5e-2567-474e71575f7b 7/5/18 10:05 AM 3235202c-c0ca-e7af-7d1b-f30a7a98ca5b 7/5/18 10:05 AM 11196f5c-436c-509b-273a-c6635b34ad75 7/5/18 10:02 AM 37bd1ddd-0d6e-f3b7-c1bb-6e27139b4856 7/5/18 9:58 AM 1b6bea03-fb6b-edb1-574b-b65122902371 1/19/18 8:45 PM Submitted Crash Reports Report ID Date Submitted bp-2efbfe1d-4642-43cc-b9ad-eae950180705 7/5/18 10:34 AM bp-7c6ddef1-6111-4889-a0e9-fc9340180705 7/5/18 10:23 AM bp-eccb4643-c69e-4ba1-bfeb-292f40180705 7/5/18 10:11 AM bp-ef8aa3d6-8158-4440-bb24-81c170180705 7/5/18 10:05 AM

more options

Crash in mozilla::dom::ContentChild::~ContentChild Bug 1401721

I do not know other than the above, it is being worked on and spiked a few versions ago.

Suggest you refresh or compile to 61.0.1 released to day : https://www.mozilla.org/firefox/all/

https://www.mozilla.org/en-US/firefox/61.0.1/releasenotes/