Updated to the latest Flash on my iMac and now it's crashing on Mozilla. Restarted my computer and it didn't work. Any suggestions?
Just updated to the latest Flash and now it's saying for the last 2 days that Flash has crashed on my Firefox on my iMac. It was working fine before then. It wasn't working at first on my Safari either after the update but after closing the browser and reopening it, Flash was working. I tried the same thing with Firefox and even tried shutting the computer off and it still doesn't work. After uninstalling and reinstalling Firefox, of which I had the latest version before it was uninstalled, Flash still doesn't work. It doesn't work for games, videos, etc, even when trying to look at the Adobe website, it still says that it's crashed. I called Adobe and they said that it's not an Adobe product problem, but a browser problem. Any suggestions?
All Replies (1)
You updated from Flash 12 to Flash 13.0.0.182, correct?
IF it is the same thing, as seems likely, it would appear to be a known issue only affecting some Macs and the work around is to downgrade by using an uninstaller and reinstall the older versions
- ATTENTION MAC CUSTOMERS - Flash Player 13 "Plugin Failure" Workaround
Apr 10, 2014 4:28 PM http://forums.adobe.com/thread/1447282- Download and run our uninstaller: http://fpdownload.macromedia.com/get/flashplayer/current/support/uninstall_flash_player_osx.dmg
- Download and run the version 12 installer from: http://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_player_12_osx.dmg
Adobe Update 4/10
We have determined that this problem is due to a compiler update in our build infrastructure that exposed a long-standing bug in a Mac system library. Flash Player now attempts to use CPU instructions that are not available on a subset of supported Mac hardware from 2006 to 2007. None of the machines in our compatibility labs are affected, so the issue didn't show up in our testing, but we were able to track down a machine that reproduces the issue yesterday. We're actively working on a fix and I'll update this post again once we have more information.
Modified by Moses