Look down the list of plug-ins for the Flash entry. After you press enter, you’ll be greeted with a list of all the plug-ins installed in Chrome (this is different from user-installed Extensions). In the address bar, type about:plugins in the address bar. How can you tell if a Flash conflict is the source of your trouble? Run Chrome. Second, while not every instance of Flash flaking out in Chrome can be attributed to a Flash install conflict, we’ve found it to be the most common reason users are experiencing Flash-related problems. You don’t realize how many web sites use Flash until every single tab locks up with a crash warning-”The following plug-in has crashed: Shockwave Flash” How Do I Know A Conflicting Flash Installation Is Causing The Crashes?įirst of all, despite the warning about Shockwave, the actual warning has nothing to do with Adobe Shockwave, which is a separate program/multimedia system from Adobe Flash. The result is serious browser lag, temporary lockup, and then a browser-wide crash of all active Flash instances. Unfortunately, things can fall apart pretty easily if Chrome gets confused and attempts to utilize both the OS installation of Flash and the internal Chrome installation of Flash. When everything goes smoothly, this isn’t a problem-the internal Flash installation is updated with every new Chrome release.

While other browsers call upon the Flash installation of the host system, Chrome includes an internal Flash installation.

The reason we’re talking about Chrome and not, say, Firefox, is because of the way Chrome handles Flash content. The following tutorial will help you get Chrome back to its speedy self. More so than other browsers, Google Chrome is particularly susceptible to a specific but not uncommon situation in which it simply will not coexist peacefully with Adobe Flash-frequent slow downs and annoying crashes are common as a result.

RELATED: How to Troubleshoot Google Chrome Crashes

Adobe shockwave updates