It pulls up a hefty list of “stuff” on the computer. Roaming the internet, I must have tried everything suggested at least once and nothing worked.įinally, I downloaded the free wise program uninstaller. I am really frustrated with both AOL.com and Chrome right now.įolks, I’ve had the same frustrating problem with Firefox - the shockwave crash popup and the computer freezing. So I again must use Safari to print from the NYT because the “box” is not covering up several sentences on the doc I print.

Just like when you use Chrome to PRINT anything on the NYTIMES website, the printer-friendly view incorporates a box of “an upcoming and related article you might wish to read”-which covers about a square inch of 3 or 4 sentences at the right side of the printer-friendly document, once you print it.

Since I have no problem using Safari to access AOL.com, it seems to me that it is only a Chrome issue affecting ONLY AOL.com’s website. And then I am getting another error message asking if I wish to continue or kill the loading page. Meanwhile, I am prevented from accessing any other sites via a Tab while the AOL.com site (via Chrome’s browser) is spinning. I have noticed only for the past two days and ONLY using AOL.com, I am getting the plugin not working or shockwave not working. Firefox installations automatically query the list and notify users before disabling the targeted add-ons.Where do I find this: Chromeâ€™s AppData folder. Mozilla has the ability to disable troublesome extensions or plug-ins by adding them to the Firefox add-on blocklist. Around the same time, Mozilla also 'blacklisted' the RealPlayer plug-in, which was contributing to the crashes. 'This is on Mozilla's end, even though they completely blamed Adobe for it,' wrote someone identified as 'Squall_Leonhart69r' on the Adobe bug database.įor its part, Mozilla had spun up a quick update to Firefox, version 13.0.1, and began pushing it to users on June 15. In its own bug-tracking database, Adobe said it could not reproduce the crash, with contributors there chastising Mozilla for blaming Adobe. There was some finger-pointing on Adobe's part as well. Initial suspicions at Mozilla pointed to Flash Player 11.3's new sandboxed plug-in for Firefox, but yesterday Adobe claimed that there were 'different causes' for the crashes, which seemed to be concentrated on Windows Vista and Windows 7 machines.

Shockwave flash player update firefox