Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

So tired of Fireforx crashing multiple times daily! Happening 2 updates ago or so. Did all the recommended fixes. Sending crash results have yielded nothing!

more options

I used to run a lot of add-ons and never had a crashing problem with FF. But with every update I have been forced to remove more and more add-ons. Now, I only have those that are really essential to me. Yet, I have more crashes than ever. FF keeps thanking me for my crash test results but never fixes anything! Maybe it's time for FF to accommodate the add-ons rather than the other way around -- since that's how it used to be. My add-ons never caused crashes. What's the good of running FF without add-ons to see if it crashes, if you really need the ad-ons? I really don't want to use IE, but FF is trying my patience to the limit. How about actually analyzing MY crash results and sending me an email that says more than "Thank you," but rather, "Here's why your crashes are occurring." Come on, guys -- get with it!

I used to run a lot of add-ons and never had a crashing problem with FF. But with every update I have been forced to remove more and more add-ons. Now, I only have those that are really essential to me. Yet, I have more crashes than ever. FF keeps thanking me for my crash test results but never fixes anything! Maybe it's time for FF to accommodate the add-ons rather than the other way around -- since that's how it used to be. My add-ons never caused crashes. What's the good of running FF without add-ons to see if it crashes, if you really need the ad-ons? I really don't want to use IE, but FF is trying my patience to the limit. How about actually analyzing MY crash results and sending me an email that says more than "Thank you," but rather, "Here's why your crashes are occurring." Come on, guys -- get with it!

All Replies (9)

more options

If you have submitted crash reports then please post the IDs of one or more recent crash reports that have a "bp-" prefix:

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You can find the IDs of the submitted crash reports on the about:crashes page.

  • You can open the about:crashes page via the location bar, like you open a website, or open the crash reports page via "Help > Troubleshooting Information".

See:


Try to disable hardware acceleration in Firefox (you need to close and restart Firefox).

more options

Cor-el, thanks for the email, as you requested, I'm posting the lastest Crash Report ID:

ID: 44cded6d-5f2a-40c7-ae31-565492131229

Perhaps you can interpret it for me.

more options
more options

Excuse my ignorance, but what is the purpose of the crash report if it does not diagnose the cause of the crash?

more options

We are users just like you and we don't have the expertise to understand all crash reports and know its cause and a possible workaround or fix for the crash. In some cases the cause is clear because some external program is involved, but this looks like an issue with some JavaScript code that could be coming from more places (code on web pages or extensions). Trying basic steps might help to isolate the cause and fix it, but I don't know a specific solution for this case.

more options

Other Crash IDs may be more useful, especially if from Firefox's safemode and with all plugin s disabled. May I ask you to try that, see if it still crashes and if so post three or four of the Crash IDs

If you try that and do not get crashes then it is all the extensions that are causing the crashes. Besides assisting in troubleshooting a good workaround may then be to set up specific additional profiles for different purposes. Let's see first of all what happens in safe mode with plugins disabled.


N.B.
It is worthwhile submitting Crash Reports, and for that matter also turning on telemetry the data does assist engineers looking at Firefox issues and performance.

If you want an individual crash report investigated you still need to report it on this forum after it has been submitted. (Filing a bug without assistance is probably not to be recommended.)

Modified by John99

more options

I understand. I thought you might have been a rep from Friefox. Happy New Year!

more options

Did you try the troubleshooting steps I suggessted then ?

And Happy NewYear to you.

more options

Hi garyd11, you wrote:

Excuse my ignorance, but what is the purpose of the crash report if it does not diagnose the cause of the crash?

In the background, software is analyzing these reports and some people are watching for trends to trying to get the "top crashers" fixed. Sometimes that is already under way when we look at the report and can see the status, but in other cases, not yet.

During the past 2 weeks, about 475 crash reports were submitted with the same signature, and the only user added comment the entire time was "fix it". That makes it hard to spot a pattern with a particular activity or website.

I agree with the above suggestion to try Firefox's Safe Mode for a while. That's a standard diagnostic tool to bypass interference by extensions (and some custom settings). More info: Diagnose Firefox issues using Troubleshoot Mode.

You can restart Firefox in Safe Mode using

Help > Restart with Add-ons Disabled (Plugins like Flash will still run)

In the dialog, click "Start in Safe Mode" (not Reset)

Any improvement in stability?

Modified by jscher2000 - Support Volunteer