There are a number of possible causes of unresponsive script errors. We have a support article listing several things to try: [[Warning Unresponsive script - What it means and how to fix it]]. Another common cause of unresponsive script errors on Windows 7 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. ---- Sorry to hear about the crashes. Two of your reports turned into links that allowed me to review the details: * July 12th: Out of memory error. With 94% of memory in use, Firefox cannot run well. And yes, the "endless scrolling" of the Facebook news feed with its auto-loading videos does consume a huge amount of memory in Firefox, so this could be a regular problem when spending a lot of time on the site. * July 4th: I check several crash reports per month and I haven't seen "CacheFileAutoLock" before. I'm not sure why Firefox would be unable to update its cache, but possibly antivirus software stepped in to clean something or a scheduled cleaning locked the file temporarily. ?? For the others, if you click the link on the about:crashes page to resubmit the report, can you load it on the crash stats server? If so, you could share the full links to the other recent reports.