ADMINISTRATOR
- Učlanjen(a)
- 11.10.2009
- Poruka
- 66.917
Typically when Flash misbehaves, your browser freezes and you get a message at the top of the screen telling you, “A plug-in (Shockwave Flash) isn’t responding,” along with a “Stop plug-in” button to push. This hardly ever works. Even more annoying, a “Pages unresponsive” box pops up shortly after offering you the option to “wait” or “kill page.” Neither will get you what you want, which is a functional Chrome browser.
That’s because neither is addressing the fundamental problem, which usually involves a conflict between Adobe Flash, which users download, and Chrome’s internal Flash installation. When both are enabled, Chrome can get confused about which to use and will try to employ both. Then you start getting old Star Trek references on your screen.
To solve the issue you’ll have to go beyond the error pop-ups that Chrome serves up and get under the Settings hood. Even though Chrome’s Settings page can be really confusing, this fix is easy. Do the following:
1. Open Chome and type this into the address bar: chrome://plugins.
2. Now you’re looking at a white screen with plug-ins listed in teeny, tiny type. Locate Adobe Flash Player (it was third down on my list), then look at the top right of your screen for the word “Details” in blue with a plus sign next to it. Click on that.
3. You should notice two versions of Shockwave Flash listed. If you see the word “Disable” in blue within the descriptions of each, that means they’re both enabled. That’s got to change.
4. Click “Disable” on the Chrome version of flash. That’s the one with the word “Chrome” in the URL presented under “Location.” That version immediately will be highlighted in pale blue.
5. Close and reopen Chrome and you should be good to go.
When that doesn’t work
If you continue to have performance issues with Chrome even after disabling one of the conflicting Flashes, check to see if there is any other software on your computer that conflicts with Chrome. You can find out by typing in the address bar: chrome://conflicts.
I got a list of 165 “modules,” none of which conflict with Chrome. But if Chrome tells you that your machine has a conflict, your options are to uninstall, disable or update it. Or not use Chrome.
That’s because neither is addressing the fundamental problem, which usually involves a conflict between Adobe Flash, which users download, and Chrome’s internal Flash installation. When both are enabled, Chrome can get confused about which to use and will try to employ both. Then you start getting old Star Trek references on your screen.
To solve the issue you’ll have to go beyond the error pop-ups that Chrome serves up and get under the Settings hood. Even though Chrome’s Settings page can be really confusing, this fix is easy. Do the following:
1. Open Chome and type this into the address bar: chrome://plugins.
2. Now you’re looking at a white screen with plug-ins listed in teeny, tiny type. Locate Adobe Flash Player (it was third down on my list), then look at the top right of your screen for the word “Details” in blue with a plus sign next to it. Click on that.
3. You should notice two versions of Shockwave Flash listed. If you see the word “Disable” in blue within the descriptions of each, that means they’re both enabled. That’s got to change.
4. Click “Disable” on the Chrome version of flash. That’s the one with the word “Chrome” in the URL presented under “Location.” That version immediately will be highlighted in pale blue.
5. Close and reopen Chrome and you should be good to go.
When that doesn’t work
If you continue to have performance issues with Chrome even after disabling one of the conflicting Flashes, check to see if there is any other software on your computer that conflicts with Chrome. You can find out by typing in the address bar: chrome://conflicts.
I got a list of 165 “modules,” none of which conflict with Chrome. But if Chrome tells you that your machine has a conflict, your options are to uninstall, disable or update it. Or not use Chrome.