Interesting...I just checked my screenshot and it's not the latest by a long shot. I tried again and (hopefully) got the latest. See attached.

Could you copy/paste the crash report IDs from the about:crashes page and post those in a reply? As you can see from working on that site, there are links to bugs, details about what Firefox was trying to do when it crashed, data from other users who had the same crash, etc. It's hard to even get started without it. Thanks.

In case about:crashes, was gibberish, please see the last section of the support article "Firefox Crashes" for steps to get the crash report IDs.

Thanks for getting back to me so quickly! Here you go, hopefully I'm doing this correctly!

Report ID Date Submitted bp-8e79eb3d-0184-4195-bf26-961332150820 8/19/2015 9:12 PM bp-c370c6e4-c155-4a9b-a758-01b522150815 8/15/2015 4:35 PM bp-948ed952-afb7-4a33-8c2e-da44e2150814 8/14/2015 5:35 PM

I didn't read very carefully: in a freeze/kill situation, the Mozilla Crash Reporter dialog generally does not come up, so we don't have any useful data on that.

There is a potential association between Flash and unresponsive script errors, and if you lengthened the amount of times scripts are allowed to spin before the error dialog is displayed, Firefox can be locked up that much longer. The culprit is the protected mode feature of the Flash player plugin. That feature has security benefits, but seems to have serious compatibility issues on some systems. You can disable it using the Add-ons page. Either:

• Ctrl+Shift+a
• "3-bar" menu button (or Tools menu) > Add-ons

In the left column, click Plugins. On the right side, find "Shockwave Flash" and click the More link. Then uncheck the box for "Enable Adobe Flash protected mode" and try that for a day to see whether it helps.

If you notice any other patterns, that might help.

The Friday/Saturday crashes are "out of memory" errors. These sometimes occur on pages with endless content, like Facebook, and in other cases when scripts go haywire or when Firefox mishandles certain content. Since it's fairly content-dependent, I'm not sure what to suggest about those.

Sometimes an update fails to complete clear old files from the program folder. The resulting mismatches can lead to bizarre and unpredictable misbehavior. To try to rule that out, you could do this:

Clean Reinstall

We use this name, but it's not about removing your settings, it's about making sure the program files are clean (no inconsistent, corrupted, or alien code files). As described below, this process does not disturb your existing settings. Do NOT uninstall Firefox, that's not needed.

(A) Download a fresh installer for Firefox 40.0.2 from https://www.mozilla.org/firefox/all/ to a convenient location. (Scroll down to your preferred language.)

(B) Exit out of Firefox (if applicable).

(C) Rename the program folder, either:

(64-bit Windows folder names)

C:\Program Files (x86)\Mozilla Firefox

to

C:\Program Files (x86)\OldFirefox

(32-bit Windows folder names)

C:\Program Files\Mozilla Firefox

to

C:\Program Files\OldFirefox

(D) Run the installer you downloaded in (A). It should automatically connect to your existing settings.

Any improvement in responsiveness?

Note: Some plugins may exist only in that OldFirefox folder. If something essential is missing, look in these folders:

• \OldFirefox\Plugins
• \OldFirefox\browser\plugins

Thanks for the help! I've removed Shockwave protected mode and will see what it does over the next day. If that fails, on to your plan 'B'. I'm thinking the out of memory failures earlier on were caused by a site that tracks lightning strikes. It's constantly ticking away this time of year in FL! I'll address that, also, and report back. Thanks!