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:

• http://kb.mozillazine.org/Mozilla_Crash_Reporter
• https://support.mozilla.org/kb/Mozilla+Crash+Reporter

I wish someone could tell me what is suddenly causing FFx to crash since I updated to v. 28 so I could get off Chrome. Here are some few crash IDs:

bp-f84aa482-db5d-4efd-8f9e-619f52140326 3/25/2014 6:30 PM

bp-72bc7d56-7dc7-4b17-80d3-5455f2140325 3/24/2014 9:23 PM

bp-14fcf566-d49a-4be2-8364-61cbd2140322 3/22/2014 3:07 PM

bp-04f6dd6f-d6f5-4172-aa91-602d52140322 3/22/2014 2:05 PM

bp-d23d7f49-f525-43a9-9105-80a6e2140322 3/22/2014 12:04 PM

bp-6ef739c3-049e-4e08-9cff-6fc922140322 3/21/2014 8:20 PM

Same issue, crashes many times a day. Here's a list: of this years crashes:

 
bp-47bcc2e9-90e3-41e1-9407-0125b2140301 01/03/2014  
bp-565a9352-58de-445b-9c1a-a08212140303 02/03/2014  
bp-c2872488-3fa4-4304-9e60-b778b2140302 02/03/2014  
bp-0fa06c7e-5f07-4df3-bf88-2491e2140303 03/03/2014  
bp-4800eb8b-7a13-4529-ab30-15df02140308 07/03/2014  
bp-047aa88e-eaac-4652-9609-6054c2140308 07/03/2014  
bp-f0008aad-289d-44fd-aef0-958712140307 07/03/2014  
bp-c895b2e7-31d1-47e4-a97e-9c3d42140311 11/03/2014  
bp-15ab282c-de19-4160-932e-cd3c92140320 19/03/2014  
bp-ca6a0050-5e3c-49d6-ab30-3ec582140320 19/03/2014  
bp-738eb731-5da2-4a31-a0ba-671a92140321 20/03/2014  
bp-778405df-de08-4cbe-bec1-522e42140320 20/03/2014  
bp-0f9095fb-bf9c-41b2-bd7d-0bbd92140321 21/03/2014  
bp-035a0d0c-4f14-45f9-a29d-5b5972140322 22/03/2014  
bp-04de9246-e001-429f-a9f7-7c37b2140323 23/03/2014  
bp-b1f6cb10-5a43-4cd4-bd8b-8e6072140325 24/03/2014  
bp-3c896334-1338-43da-b87b-f841a2140324 24/03/2014  

Hi trucker101

Your crashes are caused by an out-of-memory issue, where some process in Firefox is using up all available memory causing the OS to abort the Firefox program.

• https://support.mozilla.org/kb/firefox-uses-too-much-memory-ram

See also:

• http://kb.mozillazine.org/Firefox_crashes
• https://support.mozilla.org/kb/Firefox+crashes

Thanks for letting me know what all that means. Now to figure out why? It mostly happens when I'm on Facebook, with maybe a few more tabs open. I know when I used chrome it never crashed doing basically the same things?

You can check for issues with plugins and the plugin-container process

• https://support.mozilla.org/kb/Troubleshooting+plugins
• http://kb.mozillazine.org/Plugin-container_and_out-of-process_plugins

Thank you. I disabled all the plug ins and was able to use FFx all night with no crashes (!). Now I'll begin re-enabling them one by one until I find which one's causing the crashes. This will probably take a week or so.

It still crashes. Not as often but it still does. I think maybe I'll uninstall FFx and try reinstalling it.

Just crashed. Reinstall did not help.

bp-92003dbc-eddc-4507-bdd5-6a3782140328 3/28/2014 3:45 PM bp-b5b22767-30e5-4f6c-a96d-4dc042140328 3/27/2014 9:12 PM

Hi RikRoll,

You crashes are not the same as trucker101. Sorry if we forgot about you !

You will be getting crashes when scrolling pages containing images.

I can not say I understand the bug, but it appears there is a simple workaround that will prevent crashes until it is fixed. You need to set a couple of prefs back to their default values. Something that is done from the about:config page.

1. Type into the location bar about:config . And hit return
2. Accept any warning
3. Use the filter to find the prefs, type ge.m to narrow down the listing
4. Right click the following two prefs and toggle to the default value of true
   1. image.mem.decodeondraw
   2. image.mem.discardable

See

• http://kb.mozillazine.org/About:config

Please try that and then post back about whether it works  ?
Should it continue to crash please try in safe mode, with all plugins disabled, and the two prefs mentioned above set to the default of true and provide another couple of Crash IDs

• Use Troubleshoot Mode in Firefox
• Disable or remove Add-ons_how-to-disable-plugins

For forum cross referencing purposes

• Report for your CrashIDs
  bp-92003dbc-eddc-4507-bdd5-6a3782140328
  bp-6ef739c3-049e-4e08-9cff-6fc922140322
• Crash Signature: NS_CycleCollectorSuspect3
• Related bugs include
  967985 ASSIGNED --- Firefox 27 crashes with image discarding and decode-on-draw disabled

Not sure when it will be fixed maybe Fx29.

Thanks. The two prefs you list:

image.mem.decodeondraw

image.mem.discardable

were already set to the value of true so nothing is going to change.

I think I'll wait for v.29 to come out. In the mean time I've reluctantly made Chrome the default browser. I'm using an WinXP desktop that's due to be abandoned for support by M$ soon. I might just switch to a Linux OS and get back to Firefox then. Or does this affect all flavors of FFx?

Rik (good one!),

Are they crashes or hangs? If hangs, do they happen in Facebook when doing a dynamic search in the search box or @namelookup for tagging? That's what's killing me right now in v28...

Ric,

I am not seeing the bug on Linux. I Have not tried to check on Windows.

Possibly the same signature has multiple causes but whilst it is #9 in Windows it is #93 in Linux. There is no reason to expect your crash to be fixed in Firefox 29.
(That is easy to test if you have the inclination. I could explain if required.)

First of all as your crash does not have a known cause lets try to troubleshoot it further. Try Firefox with all plugins disabled and in Safemode if it still crashes then please paste into your next reply a couple of the Crash IDs that you get.

• Use Troubleshoot Mode in Firefox
• Disable or remove Add-ons

The crash maybe be #9 in the frequency ratings for Windows but nearly all of those will probably be solved by the workaround. Your particular crash is quite likely due to one or a combination of your addons or related to your hardware.

Complete longshot but I wonder if for instance https://addons.mozilla.org/en-US/firefox/addon/vacuum-places-improved/is involved

anticorruption,

Ric has crashes and has posted Crash IDs. This particular crash is likely to occur scrolling webpages that have images on.

You apparently have an unresolved problem and would do better to post your own question rather than asking in other peoples threads. No guarantee you will get any answer but worth a try.

HelpDesk would probably at least identify the cause of your problem if you used the profiler.

Thanks, john99. There is an open thread on my problem:

https://support.mozilla.org/en-US/questions/991572

I'm not wild about the security implications of the crash reporter, so I disabled it. So, I'm not sure if closing FF during a hang (via Win7 process ending using the close window X) generates a crash report? That's why I asked if Rik had crashes or hangs. I gather that you're implying that a hang doesn't generate a crash report?

I'm not familiar w/ HelpDesk or the profiler -- I'll do some Googling. It's very easy to reproduce the hang, so generating some telemetry shouldn't be hard. Thanks again!

Yes I had seen that, but it is not Your thread. If you post a question you are able to include your own troubleshooting information and have your own problem investigated.
Forum Guidelines do suggest starting new threads for each question.

• Use /questions/new/
  and attempt to follow the prompts to include troubleshooting information. There is a green button and and an addon to automate the process.

HelpDesk
Are the dedicated full time paid staff that now answer some of the questions.

Profiler
The profiler is a Firefox feature that generates output that I do not understand, but it does show exactly what Firefox is doing and it can be arranged so that it narrows down precisely on to what is causing a hang.

• https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler

There is a more advanced addon but that may not be necessary. Initially using an addon was the only way to do this but there is a profiler built in now.
I use Linux normally so can not use the addon myself but it is here

• https://addons.mozilla.org/firefox/addon/gecko-profiler/

If you start a new question post back here again so that others may follow it.

Telemetry
If you have telemetry turned on you will already be generating your own data that you can look at. I do not understand exactly what most of the data represents but

• See Manage Firefox data collection and privacy settings
• To view your own data use about:telemetry
• Note results of aggregated data is available here http://telemetry.mozilla.org

There is also Firefox Health Report but that is still being developed and not very exiting although it will highlight any crashes you have and your startup time.

• see Firefox Health Report - understand your browser performance
• use about:healthreport

Awesome, John -- thanks for doing the heavy lifting for me!

I have two comp sci degrees, so I was using "telemetry" generically. I had no idea that FF includes a feature that Mozilla refers to as telemetry!

I overlooked

 I gather that you're implying that a hang doesn't generate a crash report? 

Hangs do not ordinarily generate Crash Reports, other than plugin hangs

• Send plugin crash reports to help Mozilla improve Firefox

I'm not wild about the security implications of the crash reporter, so I disabled it.

Firefox probably has a pretty good policy and record on privacy. I can understand concerns will prevent people from using telemetry and crash reporting. (The Telemetry including fhr functions record private info locally & display it for you even if you opt to not submit & share data)

• http://www.mozilla.org/en-US/legal/privacy/firefox.html#telemetry
• I am not involved in any way with Mozilla data security, but I am aware whatever precautions are taken we all leave digital trails and fingerprints.
  • This is one discussion I noticed Anonymous metrics collection from Firefox
  • And another this time a blog https://brendaneich.com/2014/01/trust-but-verify/

So at least Mozilla developers do take heed of potential security risks.

If you disable crash reporting it may be difficult to help with crashes.

As long as I run FFx in "safe mode" it doesn't seem to crash (this seems odd, because when I ran it with the plug ins disabled it crashed).

I tried running it in normal mode with Vacuum Places Improved disabled as a precaution and it crashed after a few hours:

bp-775d0d46-4f6d-493e-8f3a-da2112140331 3/31/2014 2:27 PM

HiRikRoll,

Sounds like progress then and that you care able to run without crashing.

• Will it run in normal mode with Hardware Acceleration turned off ?

We often suggest troubleshooting from a base of Safemode and plugins disabled because Firefox's safemode does not disable plugins.

The problem may still include an interaction between a plugin, for instance it may only be a problem with a certain plugin IF Hardware Acceleration is used, and that is disabled in Safe Mode.

Safe mode does the following

• (See http://kb.mozillazine.org/Safe_Mode )
• All extensions are disabled.
• The default theme is used, without a persona.
• The Just-in-time (JIT) JavaScript compiler is disabled.
• The userChrome.css and userContent.css files are ignored.
• The default toolbar layout is used.
• Hardware acceleration is disabled.

If you wish to test with just Hardware Acceleration disabled there is a setting for that see

• Upgrade your graphics drivers to use hardware acceleration and WebGL#w_turning-off-hardware-acceleration

Note To test with the JIT compiler disables set the prefs javascript.options.baselinejit.* to false using about:config

• http://kb.mozillazine.org/About:config
• http://kb.mozillazine.org/Firefox_crashes#JIT_compiler