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

FF 90.0 freeze/crash issues

more options

Issue only started immediately after upgrading to FF 90.0.

I'll be browsing normal pages, the same pages I've always used that have worked, and suddenly FF will go to a white screen (including all the tabs). If I wait a moment, FF seems to decide on a whim whether to go back to normal behavior or to crash completely. There doesn't seem to be a pattern of a particular website or time that FF has been active.

I have tried reinstalling FF, updating addons, clearing cache.

All Replies (5)

more options

About how long before the problem shows?

Start Firefox using Troubleshoot(Safe) Mode {web link}

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


While still in Troubleshoot(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 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

Please, Do not post a screenshot ! !

aboutcrashesFx57

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

Helpful?

more options

Hi Fred,

The problem is sporadic so I am unsure if I can say for sure it happens at X amount of minutes. However, I was able to submit 2 reports while in Troubleshooting Mode.

Submitted Crash Reports Report ID Date Submitted bp-b4adf849-5dd4-4b52-832c-3b0b90210716 7/16/2021, 5:58 PM bp-4ab408cd-0ebe-48c1-89aa-29fba0210716 7/16/2021, 5:58 PM

I will continue to run Troubleshooting Mode while the logs are reviewed.

Thanks!

Helpful?

more options

bp-b4adf849-5dd4-4b52-832c-3b0b90210716 bp-4ab408cd-0ebe-48c1-89aa-29fba0210716 - Uptime 0 seconds Signature: OOM | small

MOZ_CRASH Reason (Sanitized) : MOZ_CRASH()

Crash Reason EXCEPTION_BREAKPOINT

Helpful?

more options

Basically, an OOM (Out Of Memory) means the system is having issues with the RAM.

https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

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

https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up

https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down


MemTest LAST UPDATED : 12/04/2020 Could you please run a tool from http://memtest.org/ in order to check the integrity of your RAM?

You will need a thumb or disk drive to install it on.


Do you let Windows handle the page file or did you set a fixed size ? Control Panel -> System -> Advanced -> Performance -> Settings

If you use a fixed size for the page file then try the former and let Windows handle the page file. How to determine the appropriate page file size for 64-bit versions of Windows {web link}

Helpful?

more options

I intentionally do not run a page file and the previous version of Firefox did not care.

What I did notice is that on the "Firefox hangs or is not responding" document, the first entry there describes about a corrupted Places file. So, I attempted this first. I renamed the places.sqlite file but did NOT find a places.sqlite-journal file to rename. I'm not sure if this could be the issue, but I thought I'd mention it in case this missing file is causing an issue. On relaunch of Firefox the places.sqlite regenerated as expected, but still no places.sqlite-journal file.

Additionally (I probably should have done this one step at a time to confirm which actually resolves the issue), I have disabled hardware acceleration. My graphics card is a RTX 3070 OC with the latest driver (471.11).

I'm not sure how Firefox could run "out of memory" with 32GB, but I will attempt to run the memtest later if this does not resolve with the renamed Places file and the disabled hardware acceleration.

I wanted to stress that this issue did not happen at all on the previous version of Firefox, but started immediately after upgrading to version 90.0. I am aware that this is a brand-new fresh release and issues may crop up, which is part of why I am reporting the issue rather than just shrugging and working around it.

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.