Showing results for 
Search instead for 
Did you mean: 

Firefox unusable after resume from hibernation

New User

Firefox unusable after resume from hibernation

Firefox is not usable after I hibernate and resume Windows.

Not usable means that the tabs and toolbar buttons do not react on mouse clicks, scroll bars do not react and new URLs cannot be entered.

This happens on Windows 7 Enterprise as well as on Windows XP SP2 with Firefox 14.0.1.

It is very annoying since I usually have many windows and tabs open and often just suspend the system to resume several hours / next day. Workaround is to kill the process in the Taskmanager andrestart Firefox.

The same issue is present with Thunderbird.

New User

Re: Firefox unusable after resume from hibernation

Looks like the problem is known in several similar forms - but still unsolved.




My problem is not with Flash, since I have the most recent version, so report does not apply.

There is also a Bugzilla report.

Would be great if somebody could take care of this eventually. :-)

New User

Re: Firefox unusable after resume from hibernation

Hey, I just posted a thread with an extremely similar issue, or possibly the same issue here:

Have you found out anything new about this? Do you also receive the dialog box with the prompt, "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete" if you wait long enough?

New User

Re: Firefox unusable after resume from hibernation

In my experience with Win XP SP3, returning from hibernation on recent versions of FF, there is a very high virtual memory usage (and to a lesser degree, physical memory usage).

There tends to be heavy hard drive activity as if it's trying to do a lot of work in VM.

If something like facebook is open that has a lot of scripts, FF will pop up a dialog saying a script is unresponsive.

Quit/saving session or just killing it in the task manager and restarting FF will allow the same tabs to load with much lower memory being utilized.

Definitely some sort of memory leak. My suspicion is it has something to do with Java, but that's just a guess.

Still, a memory leak is a memory leak and it's up to Mozilla to fix it or lose people to Chrome.