ON a mac firefox will not shutdown when shutting computer down. I is the only app. that does this. I have to repeatedly go to force quit.
I am frustrated as every time I shutdown the computer on a mac, firefox will not shutdown and hangs the computer. I have to force quit every time. So annoying that it is not my default browser anymore. I have reset firefox and have all the forum solutions- which are not really solutions at all. There are some serious problems with this browser, and no one is attending to them. All my macs are susceptible to this. Some are running on 10.7 and 10.8. Using Firefox 29. The problem happened in 28 as well.
Tất cả các câu trả lời (6)
It is best to first close Firefox via Firefox > Quit before shutting down the computer.
Well I have to force quit Firefox. That is the only way to quit it. It is the only app. that I have to that with. Why should I put up with that. Although I don't want to I have to make another browser my default browser. As I said I reset it twice already. And it doesn't save my history as well.
It is quite possible that files in the Firefox profile folder get corrupted if you force Firefox to close that way.
Firefox may need more time to close properly then the OS allows when forcing it to close.
If it works properly when you close Firefox before running down the computer then you should get used to doing it that way.
You can check for problems with the places.sqlite database file in the Firefox profile folder.
- http://kb.mozillazine.org/Bookmarks_history_and_toolbar_buttons_not_working_-_Firefox
- https://support.mozilla.org/kb/Bookmarks+not+saved#w_fix-the-bookmarks-file
- Places Maintenance https://addons.mozilla.org/firefox/addon/places-maintenance/
Places Maintenance that the profile database is corrupt and will fix it. How does it fix it? Where do I go to execute a fix? Thanks
Did Places Maintenance say that a new database file will be created when on the next start of Firefox?
No it didn't and after I restarted Firefox and ran Places Maintenance I got the same result that the database needs to be fixed. Any other ideas would be appreciated. Thanks