Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Firefox crashes

  • 4 replies
  • 1 has this problem
  • 4 views
  • Last reply by FredMcD

lethal40
lethal40
more options

Hi,

Having a number of these and also at the same time experiencing a slower response (and workablility) with firefox in general. Particularly over the last three version updates. I have found a regular site that I 'frequent' struggles with it (for months now) and a similar site also struggles. These site are online corporate bookmaker sites, so would be quite code intensive....still firefox being what it is should struggle THIS much. None of their clients apparently have raised issues with firefox.,,,i HAVE asked.

Apparently very few of my crash reports are being submitted (checked the last two). They are being 'throttled' ...dunno why or this helps.

I am not generally a lazy person...but there is an awful lot to go thru, for what maybe a simple fix...IF I can provide a the file requested (the crash files dont appear to to be effective). Once upon a time microsoft & Mozilla had file to run against ones set up to detect the reasons these appear to have gone.

Hoping to hear from someone soon

regards

lethal40

Hi, Having a number of these and also at the same time experiencing a slower response (and workablility) with firefox in general. Particularly over the last three version updates. I have found a regular site that I 'frequent' struggles with it (for months now) and a similar site also struggles. These site are online corporate bookmaker sites, so would be quite code intensive....still firefox being what it is should struggle THIS much. None of their clients apparently have raised issues with firefox.,,,i HAVE asked. Apparently very few of my crash reports are being submitted (checked the last two). They are being 'throttled' ...dunno why or this helps. I am not generally a lazy person...but there is an awful lot to go thru, for what maybe a simple fix...IF I can provide a the file requested (the crash files dont appear to to be effective). Once upon a time microsoft & Mozilla had file to run against ones set up to detect the reasons these appear to have gone. Hoping to hear from someone soon regards lethal40

All Replies (4)

FredMcD
FredMcD
more options

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Press the Reply button. Now go to the reply box and paste them in.

aboutcrashesFx29

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Some of your crash reports weren’t sent to the Mozilla Servers.

John99
John99
more options

Hi lethal40 One change off the top of my head that is a contender for issues if the fact that Firefox has been transitioning to a multi process system. That is and was a complex change and hopefully benefits most people. However it will have downsides especially on less well specified and older machines.

Crash reports often get throttled as some are more important than others and many are effectively duplicates. If you look at the very recent unsent crash reports and click some of them that should get submitted.

If you can give three or four of the recent crash IDs just the string of characters starting with bp- it may throw some light on what the problem is. Please see

And if it helps experimenting turning off multi process mode as a troubleshooting step this is how I explained it recently https://support.mozilla.org/en-US/questions/1158432#answer-963937

Running two (or more) processes should not double (etc) your ram and CPU use, and many users will have spare ram & CPU capacity.
If you have problems then at present it is not straightforward you need to use about:config to reset a couple of preferences:
  1. Use about:config by keying about:config in to the address bar, hitting the Enter Key and accepting any warning
  2. Then use the filter to search for e.au and look specifically for anything starting browser.tabs.remote.autostart there may be a number following that:
    • browser.tabs.remote.autostart = false
    • browser.tabs.remote.autostart.2 = false
  3. Use the right click option to toggle the preference to false.
lethal40
lethal40 Question owner
more options

Hi Fred McD, Thanks so much for the prompt response, and of course to you also John99. Fred McD I have followed your advise , and (force) submitted the last 7 crash reports. None of these had a leading 'BP'. They follow: b4b06426-41ee-4325-ae9e-e3fca0575a02 4/29/17 5:10 PM f8d7e904-8172-4ce1-90fb-5deedcf00fe7 4/12/17 9:28 PM e0af1800-a09c-4f59-bbd2-0935682a5f06 4/1/17 10:37 PM b92759a1-9408-4c3e-91d8-93b0642c0a9f 3/31/17 11:49 AM 386bbaee-0b8d-4e8b-97de-1fa2ada8aced 3/30/17 1:01 AM 5bf19a44-fd7a-4d6b-9631-9bd2a18799dc 3/24/17 1:13 PM 7efe9359-8fcd-4b66-bd99-bc5d69aab965 2/9/17 12:23 AM

One extra thing I would add is that the crashes are a recent development, and the slowness, freezing tying itself up...has been occuring for about 2-3 months.

I will again review the firefox crashes - troubleshooting article, and John99 post and come back

thanks

lethal40

Modified by lethal40

FredMcD
FredMcD
more options

Those reports weren't sent to the Mozilla servers.

FredMcD said

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them. The crash report is several pages of data. We need the report numbers to see the whole report.