(Also covers other reasons for crashing, besides multiple Flash Player versions, i.e. (From the horse’s mouth, and general/lots information about Flash Player in Chrome) Here are a couple of links on how to disable / enable plugin versions: Usually, one can dismiss the warning message and continue, but often the situation just keeps getting worse, with more frequent tab crashes – or ultimately the whole Chrome browser slows or crashes – which I found can only be “fixed” by closing Chrome and restarting. Or the plugin update is out of sync with the Mozilla version – often lagging, and may take months to catch up.Įither way, you may choose to manually force Chrome to use ONE version and disabling other versions, so you are using whichever version is later, especially for security to avoid vulnerabilities, so you don’t have to wait days or months.Īnother reason is to avoid conflicts from running versions simultaneously, which MAY cause the frequent crashing of Chrome tabs with the dreaded “Shockwave Flash has crashed” error. Chrome updates itself and its internal plugins whenever it sees fit (often while your computer is busy and then taking 99% of its CPU / resources), often taking days for the rollout to get to you after the Chrome updates have been released. While one can normally manually update versions of Flash Player for other browses (or even updating other browsers) by downloading an update, like for Mozilla, Chrome / Google is a control freak. One can force Chrome to use internal OR the Mozilla plugin version for two main reasons: to use the later version, and to avoid the dreaded “Shockwave Flash has crashed” error message, but there are implications…. What is confusing is that while there is a Flash Player INTEGRATED within Chrome (AKA internal) – and updated via Chrome’s own update mechanism, Chrome ALSO uses the external / plugin Mozilla version (AKA standalone), despite what Adobe says in the link below. Note, Adobe Flash Player is often referred to as Shockwave Flash Player, not to be confused with Adobe Shockwave Player (AKA Adobe Shockwave for Director).įlash Player versions (updates) can get “out of sync”, rarely for IE versus Mozilla versions on Windows (like now, 12.0.0.43 versus 12.0.0.38), but often with Chrome versions (on most platforms, not just Windows like now: 12.0.0.41), which often fall behind the Flash Player version for Mozilla. (My experience is with Chrome in Windows, since I don’t use other platforms regularly.) Chrome has many idiosyncracies – some good but many bad, like not playing nice with Flash Player – poor compatibility. This is about Flash Player in the Chrome browser. Now that Flash Player versions are “out of sync” (12.0.0.41 in Chrome 12.0.0.38 in IE on Windows 12.0.0.43 in Mozilla on Windows but 12.0.0.38 in Mozilla on Macintosh while 11.2 for Mozilla on Linux – except for Chrome! – and Solaris), I will write about this in another post. I have been promising to write about Flash Player in the Chrome browser. ![]() And why do updates “jump”? My current version is 7u45. Don’t know why I got the notification this week, but the file is dated December 20, 2013. ![]() Likewise on January 14, Adobe has announced an update of Flash Player to MAJOR version 12.0.#.# (various minor versions depending on platform + browser permutation), from verion 11.#.#.#.Īnd last but not least, Oracle has an update to the Java JRE (Java Runtime Environment / plugin) to Version 7 Update 51. ![]() In the meantime … Adobe has released Adobe Reader 11.0.06 update on January 14, a planned, quarterly update. ![]() seeing the “Adobe Reader” tag that has since been removed. Just giving z some support – and showing to others why people act a certain way (i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |