Is "Not Responding" Ever normal during startup?
Yea you are going to say its an Add-On problem. Maybe. But I can't believe that Ghostery and DoNotTrackMe can be so buggy that they just kill FF completely.
I'm in Safe Mode now or you would be seeing the troubleshooting info.
How about making the troubleshooter addon work in safe mode?
Все ответы (8)
What is the full message?
Not necessarily any console error message. But Activity Monitor shows it as Not Responding -- and its true; I cannot bring FF to be the active app, and if it is on top already, it won't respond to any input. And sometimes the chromatic spinner appears as well.
It always takes a few minutes to startup when reloading last sessions' sites (I have a DLS line, which is slow). But during the process it hangs and I have not way to figure out WHY. I presume its a slow script not being handled.
Start Firefox in Safe Mode {web link} While you are in safe mode; Press the Alt or F10 key to bring up the tool bar. Followed by;
Windows; Tools > Options Linux; Edit > Preferences Mac; application name > Preferences
Then Advanced > General. Look for and turn off Use Hardware Acceleration.
Poke around safe web sites. Are there any problems?
Then restart.
I did that a long time ago. The "use hardware acceleration when available" tab is still un-checked.
Does it work if you only disable one or both of the extensions that you mentioned?
If it works in Safe Mode and in normal mode with all extensions (Firefox/Tools > Add-ons > Extensions) disabled then try to find which extension is causing it by enabling one extension at a time until the problem reappears.
Close and restart Firefox after each change via "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: Firefox > Quit Firefox; Linux: Firefox/File > Quit)
If installed extensions cause Firefox to hang or otherwise aren't working properly then you need to disable them for now and contact the developer for support.
I can't tell if its a flaw in Session Manager, or a flaw in FF itself.
When trying to reload a session with many tabs (say over 100) it just eventually chokes.
And if the previous session was locked up and Force Quit in the first place, due to a runaway script, what built-in protections does FF have to kill that bad script when it tries to reload?
Try a fresh start of Firefox, without any session or web page. For now, just one window, one tab. Just see if there is a problem. Poke around the web. Let us know what happens.
No use trying that. It happens because something goes wrong when I'm using the 100-200 tabs that I need to have open.