Cari Bantuan

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.

Pelajari Lebih Lanjut

Win 7 Pro - 43.01 goes to "not responding" /crash within a minute

  • 2 balas
  • 4 memiliki masalah ini
  • 1 kunjungan
  • Balasan terakhir oleh otttech

more options

Also happening in Safe Mode. Uninstalled all plugins and add-ons. Refreshed Firefox - so now it only has the 2 default addons (OpenH264 and Adobe Primetime CDM) Left it with default settings so it only opens the Firefox Start page (tried previously only google.ca homepage, tried a local homepage from C:\... on my computer ). Whether I am using Firefox or just let it sit open, it becomes unresponsive in under a minute.

For the past several weeks, in version 42, it would only become unresponsive after several hours of use, multiple windows open. Memory (Private Working Set) usage by Firefox would climb up to 400-500K and my whole system would block up until I ended the Firefox Process. Even with a single window with one tab in use, it would rapidly climb to 100K immediately. It still does that with 43.01. I am not seeing usual 200-300K+ I'd been seeing because 43.01 is just not staying open long enough! Once the process ended, the rest of my system resumed normal operations.

These last couple of days with 43.01 it's impossible to use at all. I think I've managed to send off 2 crash reports today, but out of a dozen episodes, even the crash reporter is not managing to appear. Leave it for 20+minutes, it won't resume by itself, needs to be killled in task manager.

Right now it's at 115,00K and stopped at unresponsive with Mozilla start page and about:addons open.

Also happening in Safe Mode. Uninstalled all plugins and add-ons. Refreshed Firefox - so now it only has the 2 default addons (OpenH264 and Adobe Primetime CDM) Left it with default settings so it only opens the Firefox Start page (tried previously only google.ca homepage, tried a local homepage from C:\... on my computer ). Whether I am using Firefox or just let it sit open, it becomes unresponsive in under a minute. For the past several weeks, in version 42, it would only become unresponsive after several hours of use, multiple windows open. Memory (Private Working Set) usage by Firefox would climb up to 400-500K and my whole system would block up until I ended the Firefox Process. Even with a single window with one tab in use, it would rapidly climb to 100K immediately. It still does that with 43.01. I am not seeing usual 200-300K+ I'd been seeing because 43.01 is just not staying open long enough! Once the process ended, the rest of my system resumed normal operations. These last couple of days with 43.01 it's impossible to use at all. I think I've managed to send off 2 crash reports today, but out of a dozen episodes, even the crash reporter is not managing to appear. Leave it for 20+minutes, it won't resume by itself, needs to be killled in task manager. Right now it's at 115,00K and stopped at unresponsive with Mozilla start page and about:addons open.

Solusi terpilih

My issue is resolved. It was okay for another Windows user when I did "switch user" But when I switched back to my user, I got the same "not responding" again. Then I realized I hadn't rebooted in probably a week. After a slow Windows restart, Firefox is good again. Could it have been an incomplete Firefox install when FF updated - is it necessary to restart the computer as well as the browser? Or perhaps it was something in the latest Windows update left in a partial install state and wasn't finished because the computer wasn't restarted.

Did you try turning it off then back on again? Embarassingly enough, I hadn't ...

Baca jawaban ini dalam konteks 👍 0

Semua Balasan (2)

more options

- I do not have any Nvidia (which appears to be a common problem mentioned in another thread)

more options

Solusi Terpilih

My issue is resolved. It was okay for another Windows user when I did "switch user" But when I switched back to my user, I got the same "not responding" again. Then I realized I hadn't rebooted in probably a week. After a slow Windows restart, Firefox is good again. Could it have been an incomplete Firefox install when FF updated - is it necessary to restart the computer as well as the browser? Or perhaps it was something in the latest Windows update left in a partial install state and wasn't finished because the computer wasn't restarted.

Did you try turning it off then back on again? Embarassingly enough, I hadn't ...