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 57.0.2 (64-bit) stops responding to menu bar and other buttons

  • 27 பதிலளிப்புகள்
  • 6 இந்த பிரச்னைகள் உள்ளது
  • 1 view
  • Last reply by neil64

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 (20)

Please Refresh but do this 1st:

then

TEST....... If no issues then Extensions which need to be added back in 1 at a time and tested ..... Or it is your Profile : Make a new one and test ...:

If is your Profile :

Note: Any customization will revert back to default, you will also need to reinstall Extensions.

Please let us know if this solved your issue or if need further assistance.

I will try that, but could you tell me what the problem is please? Why is FF not servicing (Windows UI) messages?

Sorry not understanding your question re : Windows UI messages as you have not explained that at all.

As for the problem is possible a corrupted file or Profile.

If you are having excessive ram/cpu use you can also do this or try this 1st.

Go to the Firefox 3 Bar Menu --> Help ? --> Troubleshooting Information Page and take a look in the Accessibility section if accessibility is set to "true" there. if yes, go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check the setting to Prevent Accessibility Services from accessing your browser.

Monitor in Task Manager. Should stay below 2 gigs. If excessive then do below and monitor and change if need to.

Go the 3 Bar Menu then Options --> General --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again. Try 2 Restart Firefox after making these changes please.

Please let us know if this solved your issue or if need further assistance.

YetiYeti said

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 have the problem with the 3-Bar Menu Button in the far-upper-right. With my main FF Window, it does not respond. On certain other FF Windows, it does respond. What other icon links does not work for you?


Also, my 3-Bar Icon Button problem corresponds in any FF Window with YouTube video 'Full-Screen' icon in a video not working, also. If the 3-Bar Icon Button works in one FF Window, so does the YouTube Full-Screen Feature in that Window.

I have yet to do Testing by starting FF without Extensions, as I need to find info if that Test will retain all my Tabs, Pinned Tabs, and all FF Windows, like it does with the 'Master Exit' (Control-Shift-Q) and a restart.


- Pj

Pkshadow said

...Monitor in Task Manager. Should stay below 2 gigs. If excessive then do below and monitor and change if need to. Go the 3 Bar Menu then Options --> General --> Performance and untick everything. Change the recommended size lower then see how it runs. Note: 1 = No Multiprocessor = slow again...

I have mine at 1. Should I bump that to 2? (I know 4 was too much for me.)


- Pj

Pkshadow said

Sorry not understanding your question re : Windows UI messages as you have not explained that at all.

Windows send messages to a process when a user interacts with the UI (User Interface), e.g. WM_COMMAND. FF needs to process these messages in order to make things work when, .e.g., a user clicks on the Help menu item. If FF is not doing that, or is looping while it attempts to process a message, that might explain why FF is not responding when I click on a menu item or a button (e.g. the bookmarks button).

If you are having excessive ram/cpu use you can also do this or try this 1st.

No excessive CPU usage, even the problem is "happening". I don't know about memory usage as I didn't have any feel for what is normal. I'll see if it's approaching the 2 Gig mark.

I'll try for a clean install and see if that helps.

uninstall Firefox. Then Delete the Mozilla Firefox Folders in C:\Program Files and C:\Program Files(x86) Then restart system. Then run Windows Disk Cleanup. (Note: This should be Pinned and run Weekly, If never done below expect 10's of gig's) Then run it again and click the button that says Cleanup System Files. Note: your Firefox Profile is saved. But you should make a back up before you do :

Reinstall with Current Release Firefox 57.0.3 with a Full Version Installer

Please let us know if this solved your issue or if need further assistance.

I've done all that - and it made no difference.

The menu bar (File/Edit/.../Help) still fails to respond after a hibernate/restart, as do the bookmarks buttons in the upper top right of the window. The "new tab" button does work.

Are there any traps/traces that can be turned on so we can see what FF is doing (or rather not doing)?

One point, when I do the clean install and start FF for the first time, it tells me that that it cannot load my profile. I "OK" this and that's that, no FF running any more.

This seems odd on two counts -

if it can't access my profile I would have expected FF to give me the opportunity to create a new default profile (not just exit and leave me dead in the water). Once I restore my saved profile FF starts normally. But what if I hadn't had one?

How is FF remembering the (8-character) "random" profile name? I released all the FF folders as requested and, of course, had deleted the profile from under the Users folders. So where is the information hiding? It's not in the Registry.

Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.

Firefox uses the profiles.ini file to register all profiles and map them to a folder on the hard drive.

cor-el said

Firefox uses the profiles.ini file to register all profiles and map them to a folder on the hard drive.

OK, got it, thanks. If I'd deleted the profiles.ini file I guess FF would have created a new default profile for me and I'd be able to start it successfully after having previously deleted the profiles folder.

Curiously, this evening, when I restarted Windows from hibernation all worked well with FF! Whereas yesterday it went wrong every time.

Don't you hate intermittent bugs ;)

Just did a hibernate/reload and FF failed this time, as before. Sigh.

I have the same problems as the above posters. FF 64 bit 57.0.2 occasionally, but not always stops responding to any menu clicks, toolbar clicks, book mark clicks, etc. Even the X to close the app stops responding. I have to use task manager to close the app and restart. I run Malwarebytes and Norton to try to keep me infection free.

Thoughts?

Thanks..

Neil

neil64 மூலமாக திருத்தப்பட்டது

cor-el said

Boot the computer in Windows Safe mode with network support to see if that has effect in case security software is causing problems.

I did that, but in Safe Mode you can't do a hibernate, so I don't know if the problem would happen or not. I did leave FF running overnight, but it worked fine in the morning, but then it can do that in normal mode anyway. There's no easy way to predict when it will die (except, seemingly, nearly always after a hibernate).

Are there any trace that can be turned on that might give us a clue as to what FF is doing/not-doing when the problem bites?

neil64 said

I run Malwarebytes and Norton to try to keep me infection free.

FWIW I just run standard Windows7 security - no third party stuff.

YetiYeti said

Just did a hibernate/reload and FF failed this time, as before. Sigh.


Which 'flavor' of Hibernate do you have, 'To Memory' or 'To Disk'? (I do 'Disk' and programmed my Main Power Button to DIsk-Hibernate.)


-Pj

Pj said

Which 'flavor' of Hibernate do you have, 'To Memory' or 'To Disk'? (I do 'Disk' and programmed my Main Power Button to DIsk-Hibernate.) -Pj

To disk - I could pull the power plug out if I wished.

YetiYeti said

To disk - I could pull the power plug out if I wished.

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


- Pj

Pj மூலமாக திருத்தப்பட்டது

  1. 1
  2. 2