Frequently need to force quit Firefox 29 AFTER Command+Q
On Mac 10.9.3, when I press Command+Q to quite FIrefox 29, the application indeed does disappear from the screen. But about a third of the time it has actually hung. I can't re-open Firefox unless I first force quite it.
Izabrano rješenje
Hi bbincc,
Sorry you are having problems with Firefox.
You should not close Firefox by killing the application or process unless that is absolutely necessary e.g.it has locked up.
Firefox needs to closed own in an orderly manner and you should close Firefox using the Firefox menu. (Although using Command+Q should work as long as that is the shortcut indicated on the menu)
Please use
- New Button
→ Quit 
Closing Firefox improperly and other close down issues sometimes create multiple sessionstore files, sometimes that can cause hangs and the solution is to delete the multiple files.
Currently Firefox sometimes has an issue with not closing down properly if you have set Firefox to clear History at closedown. This is a known problem mainly seen in Firefox 29 and people are working on trying to fix that, although the Fix is unlikely to be before Fx30.
The workaround is to not set Firefox to clear History when it shuts down, instead set it to remember History.
- Use New Button -> Preferences -> |Privacy| History Firefox will: [Remember History v]
- Note you should be able to use a private browsing window if that
helps. You may need to close that window before exiting from Firefox
Please try following the advice and post back with how you get on.
Please say whether or not you have Firefox set to clear History at shutdown ?
(Full troubleshooting information was not provided when the question was asked)
All Replies (4)
Odabrano rješenje
Hi bbincc,
Sorry you are having problems with Firefox.
You should not close Firefox by killing the application or process unless that is absolutely necessary e.g.it has locked up.
Firefox needs to closed own in an orderly manner and you should close Firefox using the Firefox menu. (Although using Command+Q should work as long as that is the shortcut indicated on the menu)
Please use
- New Button → Quit
Closing Firefox improperly and other close down issues sometimes create multiple sessionstore files, sometimes that can cause hangs and the solution is to delete the multiple files.
Currently Firefox sometimes has an issue with not closing down properly if you have set Firefox to clear History at closedown. This is a known problem mainly seen in Firefox 29 and people are working on trying to fix that, although the Fix is unlikely to be before Fx30.
The workaround is to not set Firefox to clear History when it shuts down, instead set it to remember History.
- Use New Button -> Preferences -> |Privacy| History Firefox will: [Remember History v]
- Note you should be able to use a private browsing window if that
helps. You may need to close that window before exiting from Firefox
Please try following the advice and post back with how you get on.
Please say whether or not you have Firefox set to clear History at shutdown ?
(Full troubleshooting information was not provided when the question was asked)
I've never closed Firefox by killing Firefox, only by selecting "Firefox > Quit Firefox" or by using the menu's indicated keyboard shortcut: Command+Q.
I do, however, set Firefox to clear History at close, and I see now that that's causing the problem. Thanks! Good to know what's going on, and the workaround, and that developers are working on a fix. Thanks again!
Thanks for posting back good to know the workaround helps.
What appears to be the main one for the clear History issue may still make it into Firefox 30 or Fx31
- (Bug 965309 - Worker hang at shutdown with XHR )
Thinking aloud
Just looking at the bugs we may need to wait for firefox 32 for a proper fix to some of them that will be September, however I hope those are only the ones already cured by Firefox29.0.1
- Fx 32 fix- Bug 985655 - [AsyncShutdown] Ensure that Sqlite.jsm doesn't shutdown before its clients
- This was definitely worked around with Fx29.0.1 so not urgent
Bug 966469 - Slow queries in netpredictions.sqlite
Sounds good. Knowing it's being worked on, I don't mind waiting.