Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

I bought a 64 bit acer with 32 bit mozilla installed and upgraded to 64 bit mozilla and it keeps crashing. Back to 32 bit?

more options

FF keeps crashing. I was surprised to see the 32 bit installed on a 64 bit, so I uninstalled and upgraded. Per FF info on the forum.

Don't know if it's because I don't religiously reboot. Could be windows 10. Wish they would support my old mac, it's so much better than this crap. It is so frustrating because I keep a couple of browsers open, one with job links and the other is what I like to read. It's eating all my memory. I have no other apps or anything going.

FF keeps crashing. I was surprised to see the 32 bit installed on a 64 bit, so I uninstalled and upgraded. Per FF info on the forum. Don't know if it's because I don't religiously reboot. Could be windows 10. Wish they would support my old mac, it's so much better than this crap. It is so frustrating because I keep a couple of browsers open, one with job links and the other is what I like to read. It's eating all my memory. I have no other apps or anything going.

All Replies (5)

more options

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, and then post some of the recent ones here.

However, if you are getting a Windows crash dialog (usually a couple lines of large text), Firefox usually wouldn't have log information.

Or if Firefox is "not responding" that's a different issue, see: Firefox hangs or is not responding - How to fix.

Also and/or meanwhile, could you test in Firefox's Safe Mode? That temporarily deactivates extensions, hardware acceleration, and some other advanced features of Firefox that might make it more prone to crashing on some systems.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any less crashy?

more options

It's a mozilla problem. I have used the crash reporter. It seems to eat my memory, which is why I'm wondering if I should go back to the 32 bit version. Windows 10 keeps giving me memory alerts, so when I check, FF is eating up 95% without having any apps running or any other programs.

If I go back to the 32 bit will this solve my problem?

more options

I won't know if that works for a few days but darn, it disabled my adblock.

more options

Note that Adblock Plus that shows in the System Details list has been reported to cause memory issues.

You can try uBlock Origin instead.

You can also try to update your graphics display driver.

more options

If you have used the Mozilla crash reporter for this problem, can you post some crash report IDs?

Of course 32-bit Firefox can't use nearly as much memory as 64-bit Firefox, so more memory should remain available if you switch back. That said, Firefox will run out of memory sooner, so it might not be a better experience.