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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Firefox 57.0.2 (64-bit) stops responding to menu bar and other buttons

  • 27 freagra
  • 6 leis an bhfadhb seo
  • 1 view
  • Freagra is déanaí ó neil64

more options

I installed the latest-n-greatest version of Firefox (57.0.2) for Windows-7 last week. It loads and works fine, but after some indeterminate period of time FF stops responding to button presses or items on the menu bar. And after a hibernation (even if this is immediately after starting FF), the above problem always happens.

Running in Safe Mode makes no difference.

I had no problems with the previous version of FF.

I installed the latest-n-greatest version of Firefox (57.0.2) for Windows-7 last week. It loads and works fine, but after some indeterminate period of time FF stops responding to button presses or items on the menu bar. And after a hibernation (even if this is immediately after starting FF), the above problem always happens. Running in Safe Mode makes no difference. I had no problems with the previous version of FF.

All Replies (7)

more options

Pj said

Hmm. Works for me with FF and everything else I have up and running. Might be some other power or sleep-state setting(s).

Just failed now (as expected) as I brought the computer out of hibernation.

Hard to see what could be upsetting FF after hibernation, but then I don't really understand the ins and outs of hibernation - there must be a lot of complex work to do under the hood. And FF has also failed without a hibernation (as per Neil64's "me too" post), just not so often. So I think it's probably not worth concentrating entirely on hibernation.

Where now?

more options

Just for clarity, I have a desktop PC with no hibernation or power saving settings enabled.

more options

FF just failed without a hibernation - I left it sitting there for about four hours and when I came back it wasn't responding to the menu or most buttons. Nothing to do with power-saving here then.

I do wonder if it's something to do with the multiple FF processes that are running? Perhaps the one that has the focus thinks it doesn't need to process WM_COMMAND (or WM_SYSCOMMAND in Neil64's case) messages? I've set the content process limit to 1, but there are currently four instances of firefox.exe running. I can't remember how many there were in older releases. Just one?

Somebody somewhere in the FF development team must know how to check/trace this, else we're going to spend our time just guessing at what it might be!

more options

YetiYeti said

FF just failed without a hibernation - I left it sitting there for about four hours and when I came back it wasn't responding to the menu or most buttons. Nothing to do with power-saving here then.

What type of system do you have? Memory? You don't have ALL Tabs active at once? How Many? I have my FF set to open one Tab per window, so it loads any other Tab as I visit each Tab as needed. My Main FF window probably has around 300 Tabs up, waiting for an 'active' visit. I have 6 other windows open at this time.

I usually can go for days before I Master Exit FF and start it up again, and sometimes a Windows-7 Pro SP1 reBoot about once a week or two.


- Pj

Athraithe ag Pj ar

more options

Pj said

What type of system do you have? Memory?

A Intel i5 laptop running Windows 7 Professional. With 4GB of memory.

You don't have ALL Tabs active at once? How Many?

All my tabs (typically three or four) run in a single window, except when I click on a link in, say, Thunderbird in which case a new window appears. The problem has happened with just a single tab.

Athraithe ag YetiYeti ar

more options

Has there been any progress on this problem?

If I leave the laptop alone for an hour or so, then when I come back FF is usually showing the problem and I have to kill FF and restart it if I want to use any of the menu buttons. It's a damn nuisance.

more options

YetiYeti said

Has there been any progress on this problem? If I leave the laptop alone for an hour or so, then when I come back FF is usually showing the problem and I have to kill FF and restart it if I want to use any of the menu buttons. It's a damn nuisance.


Me too. I have to kill it using task manager.

  1. 1
  2. 2