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

Firefox crashes constantly

  • 3 svar
  • 5 har dette problemet
  • 4 views
  • Siste svar av blebadef

more options

Firefox is crashing all the time, this has been going on for the last few days, there are hours when it's stable and other times when it crashes once per minute.

This are the two last reports.

bp-ecd54a8b-acd8-4686-aa16-24ace2140626
bp-3102bfa3-79da-495e-9312-e906b2140626
Firefox is crashing all the time, this has been going on for the last few days, there are hours when it's stable and other times when it crashes once per minute. This are the two last reports. bp-ecd54a8b-acd8-4686-aa16-24ace2140626 bp-3102bfa3-79da-495e-9312-e906b2140626

Endret av cor-el

All Replies (3)

more options

Does Firefox crash when you access secure https web pages or also with normal http links?

Try to rename the cert8.db file in the Firefox profile folder to cert8.db.old or delete the cert8.db file to remove intermediate certificates that Firefox has stored.

If that helped to solve the problem then you can remove the renamed cert8.db.old file. Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previous intermediate certificates. Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.

If that didn't help then remove or rename secmod.db (secmod.db.old) as well.

You can use this button to go to the currently used Firefox profile folder:

  • Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)

Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem

more options

Thanks, I tried renaming/deleting the files proposed but they didn't work, in the end I decided to get a new profile, I saved all the archives necessary and so far so good. Hope it doesn't crash although I doubt it =P.

more options

This happened to me at one point, and I found out that one of my RAM chips had gone bad. The way I found out was from scanning with Memtest86. Its an ISO file that you print onto a CD, then the computer will boot from it. After replacing the chip it has been running smoothly ever since.