This may not fix every Shockwave Flash problem, and some of you may find only one version installed.  You will need to restart the browser for the change to take effect.  Now, disable Chrome’s internal Flash installation which is located in Chrome’s AppData folder. If you find multiple versions of the plugin installed then click the "+" toggle to expand the entries for the plugin.  If you notice multiple versions then this is causing your problems.  Scroll down to find the Flash plugin and pay attention to if there is more than one version installed.  Type "chrome:plugins" to open a page that will display all of the installed plugins. To get started, open Chrome and click in the address bar.
There you may disable Flash altogether, change its default status, or whitelist or blacklist it.
You can manage Flash functionality by loading chrome://settings/content in the browser and selecting Flash from the listing. The chrome://plugins page is no longer available and the method described below does not work anymore because of it and because Google added Flash to Chrome internally. Update: Google changed how plugins are managed in the Chrome browser.
 It may not solve all of Adobe's woes, but it should at least stop the plugin crash that ruins so many browsing experiences.  It's annoying and slows the browser to a crawl.įortunately, there is a fix for this common problem that is fairly simple for even a beginner user to handle.  This can also be followed by a popup from Chrome asking if you want to close "unresponsive tabs". Generally speaking, what users experience is the following: a web page or tab freezes in Chrome and that is followed by a message under the menu bar stating that "Shockwave Flash has crashed".
 This isn't a security hole, but simply a problem with the extension crashing and causing Chrome to have problems of unresponsiveness.  The software maker has dealt with numerous security issues with Flash, Reader and their other apps. It's likely not a Google problem, but an Adobe one.