Given that the bulk of this thread is from 2014 and the majority of the advice is related to NPAPI Flash Player in Chrome, which is no longer supported, I'm going to lock this thread.
There was a recent bug in Chrome, which significantly impacted Flash performance. My understanding is that the issue has been resolved in current Chrome builds.
If you're having a problem still, the best path to a resolution is to provide a detailed description of the problem so that we can inspect it directly, on a comparable machine. The long "me too" threads, particularly the ones that span years, are generally not actionable, which is why they continue to persist. When we can have a direct dialog with an individual for troubleshooting, or where we can directly reproduce and inspect a problem, it typically gets resolved quickly and efficiently. The exceptions are generally where we're running into real limits of underlying technologies in the operating system or parent browser (and in those cases, there's usually long-running behind the scenes work happening when the vendors in question are interested in working with us to address the limitations).
In many of these kinds of threads, there's general confusion about the fact that a generic symptom (the slow script dialog, a crashed plug-in dialog, etc) doesn't necessarily represent a single, distinct problem. When I start teasing these kinds of threads apart, I usually end up with a dozen distinct problems, most of which are related to drivers on the user's system and/or inefficient content.
While we're genuinely interested in fixing issues and making the web better for everyone, we need detailed, actionable data in order to reproduce, investigate and resolve problems.
To that end, if you're having problems, feel free to mention me (type the at symbol and my name) in a forum post, and include the basic set of details describe here, and I'm more than happy to try and help:
https://forums.adobe.com/thread/1195540
Thanks!
29
Replies
AdChoices