Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

While still in Safe Mode,

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. Now go to the reply box and paste them in.

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.

Thank you very much for the fast reply, FredMcD. Unfortunately, I am unable to launch Firefox in safe mode--neither method works (shift key or command line).

I have uninstalled and reinstalledFirefox, but same problems occures: won't launch, immediately goes to Crash Reporter, can't submit crash report, can't launch in safe mode.

The best I can do (with my skills) is paste the details here of what is shown in the Crash Reporter. Does that information provide any insight on how to correct the problem? Thank you again.

AbortMessage: ###!!! ABORT: new XPCJSContext failed to initialize.: file c:/builds/moz2_slave/m-esr52-w32-000000000000000000/build/src/js/xpconnect/src/XPCJSContext.cpp, line 3474 AvailablePageFile: 3916128256 AvailablePhysicalMemory: 1789202432 AvailableVirtualMemory: 1864380416 BlockedDllList: BreakpadReserveAddress: 404553728 BreakpadReserveSize: 67108864 BuildID: 20170802111520 CPUMicrocodeVersion: 0x60c CrashTime: 1505107750 Email: [I have removed my email address] InstallTime: 1502314849 MozCrashReason: MOZ_CRASH() Notes: xpcom_runtime_abort(###!!! ABORT: new XPCJSContext failed to initialize.: file c:/builds/moz2_slave/m-esr52-w32-000000000000000000/build/src/js/xpconnect/src/XPCJSContext.cpp, line 3474) ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384} ProductName: Firefox ReleaseChannel: esr SafeMode: 0 SecondsSinceLastCrash: 161 StartupCrash: 1 StartupTime: 1505107750 SystemMemoryUsePercentage: 44 Throttleable: 1 TotalPageFile: 5174689792 TotalPhysicalMemory: 3198107648 TotalVirtualMemory: 2147352576 URL: UptimeTS: 5.087875 User32BeforeBlocklist: 1 Vendor: Mozilla Version: 52.3.0

This report also contains technical information about the state of the application when it crashed.

This is the prior version of Firefox ESR https://ftp.mozilla.org/pub/firefox/releases/45.9.0esr/

See if the problem is still there.

Thank you again, FredMcD. I got the same result after installing 45.9.0esr--I try to launch Firefox, it crashes with Crash Reporter appearing, and I'm unable to submit report. This is all is baffling to me as a previous version of FF should have done the trick. The fact that Chrome and IE are still functioning properly adds to the frustration.

I believe this may end up being unsolvable, but do you have any other suggestion for me (other than getting a new computer)? Thank you very much.

Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches.

You will need to restart Firefox for this to take effect so save all work first (e.g., mail you are composing, online documents you're editing, etc.,) and then perform these steps:

In Firefox 54 and below:

1. Click the menu button and select Options (Windows) or Preferences (Mac, Linux).
2. Select the Advanced panel and the General tab.
3. Uncheck Use hardware acceleration when available.
4. Close Firefox completely and then restart Firefox to see if the problem persists.

In Firefox 55 and above:

1. Click the menu button and select Options (Windows) or Preferences (Mac, Linux).
2. Select the General panel.
3. Under Performance, uncheck Use recommended performance settings. Additional settings will be displayed.

   

4. Uncheck Use hardware acceleration when available.
5. Close Firefox completely and then restart Firefox to see if the problem persists.

Did this fix your problems? Please report back to us!

If the problem is resolved, you should check for updates for your graphics driver by following the steps mentioned in these Knowledge base articles:

• Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

• Upgrade your graphics drivers to use hardware acceleration and WebGL

Thank you.

Try to disable multi-process tabs in Firefox. You can disable multi-process tabs in Firefox by setting the related prefs to false on the about:config page.

browser.tabs.remote.autostart = false browser.tabs.remote.autostart.2 = false

http://www.ghacks.net/2016/07/22/multi-process-firefox/

Type about:config<enter> in the address bar. If a warning screen comes up, press the Be Careful button. At the top of the screen is a search bar.

Thank you FredMcD. I am not able to start Firefox at all; in other words, I never have an opportunity to access the menu button to change settings because FF never materializes. It crashes immediately and Mozilla Crash Reporter appears.

I don't know how to change settings if the application never launches. Is there an "offline" approach???

Thank you very much.

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

Sorry, please see an earlier part of my post. I am unable to launch FF in safe mode using either method: holding shift key to launch doesn't work, nor does using the command line. Both methods result in Mozilla Crash Reporter, which again is unable to submit the crash report.

are you using quickheal security software by any chance?

Thank you very much for jumping in, Philipp. No, I'm using Avast and Malwarebytes. Baffling.

Please perform the following steps to give us a crash report ID that helps us find out more about the cause of the crash.

1. On the keyboard, press [Windows] The image "Windows key" does not exist. + [R]. This should bring up a Run window that contains a text field.
2. In that text field, type %APPDATA% and press Enter. An explorer window should open.
3. From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
4. Now, you should see a list of files that contain reports. Go to View > Arrange Icons by > Modified to get the most recent files at the top of the window.
5. Open the most recent 5 files with a text editor and copy the IDs.
6. Paste each ID with bp- into the reply window on the forums.

Thanks in advance!

Thank you very much, Philipp.

The last successfully submitted crash report is from 2011 (ugh: Crash ID: bp-3624183a-99ce-4dae-af79-94b192111212).

None of the recent crashes appear in the submitted folder, which may make sense because now when I either "restart" or "quit" from Mozilla Crash Reporter, a short message appears at the bottom of the window, "There was a problem submitting your report." (I am connected)

However, I do have current files in the "Crash reports/pending" folder (DMP and .extra files), as well as another small file in "Crash reports" named "LastCrash."

Are those of any value? Thank you again for continuing to help me figure this out.

thanks, we delete crash reports from the servers after a year, so that won't help. there are some user comments to similar crashes saying the problem disappeared when they changed some settings or uninstalled malwarebytes - try to disable its webshield for a start...

You are correct. Malwarebytes 3.2.2 is causing Firefox to crash on XP. Turning off self-protection mode in Malwarebytes 3.2.2 allows FF to launch as it should.

As you suggested that Malwarebytes might be the cause of Firefox crashes on XP, I researched that angle and found this very recent thread on the Malwarebytes support forum: https://forums.malwarebytes.com/topic/209334-install-3222018-and-firefox-5230-crashes/

Malwarebytes admits that turning off self-protection mode is a workaround and not a solution. Hopefully MB will develop a fix soon.

Perhaps this information can be shared with other FF users on XP running MB 3.2.2

Thank you very much for your help and persistence diagnosing this issue. Well done.