![பயர்பாக்ஸ் logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Firefox crashes
Hello,
Firefox crashes constantly at startup after the update from yesterday. I tried to start in safe mode and to create a new profile but with no luck. Every time I click on the icon the program crashes.
Any help much appreciated.
All Replies (9)
Hi apari, sorry to hear about the crashes.
If you are getting the Mozilla Crash Reporter form, your Firefox may have logged some data that would help track down the cause of the problem. You can submit that data to Mozilla and share it with forum volunteers to see whether it points to the solution. Please check the support article "Firefox crashes - asking for support" for steps to get those crash report IDs from the about:crashes page -- or if necessary from disk -- and then post some of the recent ones here.
I have this problem too.
Started after upgrading to ver. 56.0.1 (64 bit)
Sent in 3 Crash Reports.
Will forward a 4th Crash Report when I log out, and then close FF.
User54 மூலமாக
I have this problem too.
Started after upgrading to ver. 56.0.1 (64 bit)
Sent in 3 Crash Reports.
Will forward a 4th Crash Report when I log out, and then close FF.
Hi User54, could you please start a new question for your crashes. It's hard enough keeping one person's crash data straight!
https://support.mozilla.org/questions/new/desktop/fix-problems
As always, scroll down past article suggestions to continue with the question form.
Reports were submitted to Mozilla via the Firefox error message interface. No luck. I have tried safe mode, re-creating profile, re-installing from scratch. How on earth can a simple update destroy a perfectly working program is beyond me. I am ready to switch to Chrome (sigh!)
Take a look at the topic, "Firefox Crashes", and my reply:
OK. A bit of a problem getting the 3rd upgrade in one week to take effect.
Anyway, now running with FF ver. 56.0.2 (64-bit).
When FF starts, it opens THREE Tasks in Task Manager.
When FF Exits, it closes THREE Tasks in Task Manager.
Now, there are NO ERROR Messages that POP-UP.
Problem solved,
apari said
Reports were submitted to Mozilla via the Firefox error message interface. No luck.
Hi apari, I realize this is frustrating. However, in order to give you comments on your crash reports, we need to know the report IDs. In the article I linked earlier, there are two methods to get those report IDs: open the about:crashes page (difficult if Firefox keeps crashing) or find them on disk. Here's the link again: https://support.mozilla.org/kb/firefox-crashes-asking-support
Another thing to consider:
One of the main effects of the Firefox 56.0.1 update was to migrate 64-bit Windows users from the traditional 32-bit version of Firefox to the 64-bit version. We've received a number of puzzling reports of Firefox either not starting (probably due to incompatibilities with 64-bit drivers that Firefox expects/requires) or not loading any pages after this migration. And in some cases, crashing at startup.
That's why I would really like to see your crash reports. However, if you do not have the patience for that right now, it is worth trying a return to 32-bit Firefox.
While normally this kind of change is seamless -- the installer detects your existing data and preserves everything -- you might want to make a backup "just in case."
- Back up and restore information in Firefox profiles
- How to opt out of 32-bit Firefox migration to 64-bit
Note: If you decide to try 64-bit Firefox on the same system at some point in the future, see: How to switch from 32-bit to 64-bit Firefox.
Hi apari, thank you for the report ID.
In that report, Firefox crashed when interacting with software that appears to be a part of Webroot SecureAnywhere. I don't know if that is a new incompatibility caused by an update to Firefox or an update to Webroot, or a one-time thing.
Could you trigger Webroot to check for updates in case that helps?
You also could experiment with the WebShield settings if updating doesn't help. In particular, you could turn of the feature of activating browser extensions: