I get the same freeze on resume and my laptop lid is set to hibernate (not sleep).

FF 22.0 Win 7 64bit Wired ethernet (no Wifi) Asus laptop in case that makes a difference

Point of interest: Firefox unfreezes gradually. The attempts to change the active tab and add new tabs start to happen gradually after 4-5 minutes with 10-15 seconds between actions. Within a minute of super sluggish response it will recover full responsiveness.

Forgot to check the FF CPU usage during the total freeze and the sluggish response. Could give a hint as to what FF is doing.

I've also had the same problem on my desktop pc on Win7 64-bit.

This was a while ago, however. I've no idea if it still does it.

My solution was simply not to let it go to sleep.

Sorry it took me so long to respond, but FF was frozen :-)

I think that I checked the memory and HD usage of FF with Task Manager when this occurred. I did not notice anything unusual...no abnormal memory usage or HD thrashing.

I hope the Mozilla team can get to the bottom of this! I do not want to have to use Chrome or IE, but this is getting tiresome and Mozilla does not seem to have any solution.

alanamar solved the problem by not allowing sleep, but that is not an acceptable solution. My computer is unused for many hours each day.

yoyoma2 was willing to wait (for a long time) to do any browsing. 5 minutes is too long to wait! I would rather open another browser or close and restart FF in order to get on with my work.

I get this problem too - on a tower PC (Windows 7 64-bit) connected by Ethernet, whenever waking from a lengthy (estimate 30 minutes or more - although I haven't timed it) sleep.

No problems on my laptop (Wifi, Windows 7) which usually spends much more time asleep.

Getting very frustrating!

I am running Windows 7 FF 22. I found that when my computer sleeps or hibernates that firefox won't allow me to do anything. I've reset firefox, uninstalled and reinstalled it. Still having the same problem.

I know this is frustrating, but I don't experience this myself (or at least the delay is not noticeable), so I don't have any insight into it.

In looking at the bugs on file in the bug tracking system, several people have reported the problem but it seems the developers do not have enough leads to figure out where the problem lies. In particular, they would like someone to try various nightly releases of Firefox to determine which day's changes cause the problem. (This is to identify the "regression" range.) Due to the nature of the problem, this requires a huge amount of patience...

If it could be linked to particular add-ons then it might be easier to address.

If someone who experience this problem is putting Windows to sleep or leaving the computer for a long enough time that Windows will sleep, could you flip Firefox into Safe Mode to see whether the problem still occurs?

Because session restore is an imperfect technology, if you cannot afford to lose your open windows and tabs, you may want to bookmark them.

Firefox's Safe Mode is a standard diagnostic tool to bypass interference by extensions (and some custom settings). More info: Diagnose Firefox issues using Troubleshoot Mode.

You can restart Firefox in Safe Mode using

Help > Restart with Add-ons Disabled

In the dialog, click "Start in Safe Mode" (not Reset)

Any difference when waking from sleep?

To restart in normal mode, you would exit Firefox, then restart Firefox. You can restore your session using the History menu or the button on the built-in Firefox home page.

My problem started yesterday afternoon and consistently happened every time I was in sleep or hibernate and "woke" my computer up. I removed ALL add-ons and only kept my history, cookies, and favorites. I'll try safe mode next- I was getting ready to try it anyway.

Well, safe mode did work. Now to figure out why.

Then, I ran FF not in safemode and didn't have a repeat.

Hi springsgardner, Firefox is prevented from using hardware graphics acceleration in Safe Mode. Since graphic driver incompatibilities cause a lot of random issues in Firefox, you might want to disable that manually.

You usually need to restart Firefox in order for this to take effect, so save all work first (e.g., mail you are composing, online documents you're editing, etc.).

orange Firefox button (or Tools menu) > Options > Advanced

On the "General" mini-tab, uncheck the box for "Use hardware acceleration when available"

As described in the Safe Mode article, the "just in time" (JIT) JavaScript compiler also is disabled in Safe Mode. That's a little harder to disable manually. (I don't recall the steps off the top of my head.)

As per the request, I ran FF (ver 22.0) in safe mode. No joy. It still freezes upon awakening from sleep.

Thanks. I tried unchecking "Use hardware acceleration when available"and still had problems. It was still extremely slow. I don't think I had this problem until I upgraded to v 22.

I took it a step further and disabled all add-ons. Still no luck.

It will be nice to step away from FF for a while and let my computer sleep or hibernate, then come back and use it again without shutting it down.

Hi Econdoc and springsgardner, thanks for testing Safe Mode. Since that doesn't make any difference, it could be something in the pages themselves, i.e., scripts, plugins, refreshes... This is looking hard to pin down.

When I put my computer to sleep (using the keyboard Fn + "moon" key) I usually minimize all the application windows first so I'm just looking at my desktop. Not sure whether it makes any difference in Firefox's behavior if it is not the "active" application, but worth a test.

Fingers crossed - but I may have solved this.

After becoming increasingly exasperated with the effects of Flash (videos crashing, frequent Runtime "feedfade" errors, yesterday - after trying the latest version (11.7) of Flash with zero improvement (on Firefox 22.0), I reluctantly followed the tip to downgrade to Flash 10.3.

Since then - no Flash crashes, no Runtime errors and - at least so far - the problem on waking from sleep seems to have gone away. Result!!

I don't like the idea of using outdated software but if it avoids all these frustrations and time wasting, the risk seems to be worth taking.

My instinct exactly! I felt like FF was fine until I updated something (I thought it was Java but it must have been Flash). Thanks so much for figuring it out. So now we have a workaround. What's the next step to getting the bug squashed? Have Moz contact Adobe? Or have Moz trap the bug?

I don't seem to have the 10.3 files still in my download folder so I may downgrade. Where/How did you get a hold of flash 10.3?

Hi springsgardner, Adobe has ended support for Flash 10.3 and removed it from the last URL I have for it: http://www.adobe.com/special/products.../fp_distribution3.html.

The most consequential difference between Flash 11.3 and higher compared with earlier versions is the addition of protected mode for Windows Vista and higher. If you have not already tried it, you can disable protected mode by manually editing a configuration file.

See this support article from Adobe under the heading "Last Resort": Adobe Forums: How do I troubleshoot Flash Player's protected mode for Firefox?

This may or may not be related in reference to Flash, but Firefox has a lot of trouble playing anything on HBOGO. The video is highly jittery, or stuttery, and quite unwatchable.

And Chrome won't play it at all. This is the only site I have this kind of problem on.

I can't believe HBO could be unaware of this problem, but it may be some idiosyncratic interaction of something on my computer with Flash.

This thread seems to have drifted from the topic in the title.

FLASH PLAYER

• Adobe post about 10.3 support ending http://blogs.adobe.com/flashplayer/2013/05/extended-support-release-updated-to-flash-player-11-7.html
• Adobe archive site intended for developers http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html

SLEEP PROBLEM
If anyone can reliably produce this problem, and is willing to try to prove it is a Firefox problem then there is a special tool that helps in finding regression windows.

A regression Window is the range in which the fault appeared. The tool (called mozregression ) installs and starts an additional version of Firefox, and waits whilst you test that. You report back either that the tested version is good or bad, it then uninstall that and reinstalls a different version. After a number of cycles the range is narrowed down, usually to a very specific start date.

With this information developers can look at a known problem and themselves discover the likely change that caused the problem and reverse the change or otherwise fix the problem.

Instructions (Bug 8373110 c14)

Many people say the issue have appeared since FF21 or FF22. So maybe there is a possible regression in one of these versions.

For users who are able to reproduce the issue every time, could you use the tool mozregression (see http://harthur.github.io/mozregression/ for details) to find a regression range (provide the changeset).

FF21 nightlies started in Jan 2013 (mozregression --good=2013-01-01).

You need to define a workcase: set a power on-off session easily usable so you'll be able to wake up your machine fastly after mozregression downloaded and launched the nightly build.

If anyone with a problem wants to try the above it will be helpful. (Maybe check the bug before starting in case the information has already been provided)

The Flash idea is great if it really works. Has anyone else substantiated this? Since I have run FF in safe mode (no extensions/no plug-ins), I am a little skeptical about the Flash connection. I had the same freeze problem in Safe Mode, where Flash should never have been an issue.

Hi Econdoc, Safe Mode doesn't disable plugins (like Flash), only themes and extensions.

That doesn't mean Flash is a cause of post-sleep lethargy for everyone, but it could be relevant to some users.

Removing Flash didn't help me. It never mattered what was on the pages I had opened, I ran into this problem and my browser never recovered. The really odd thing that did work: Click on the FF Icon in the task bar. Whatever link I clicked on would "magically" appear after I clicked the icon twice. Naturally, this would be time consuming and frustrating. So, I closed FF and restored my previous session.

I followed a lot of the suggestions such as resetting FF, disabling add ons and enabling them one at a time, and opening FF in safe mode. It wasn't until after I opened FF in safe mode the third time, followed by opening it normally, that this problem disappeared. I haven't had this problem in 24 hours.