Flex application became slow on mac since flash player 23

Report · Oct 13, 2016

Hello,

Since the release of the version 23 of the flash player, we experience several issues on mac computers with a Flex-based application:

- on Chrome and Firefox, some pages now take 5 or 6 times more than before (or compared to other OS computer) to display

- on Safari display times are better BUT scrolling events (from the mouse wheel) are not passed to the application by the browser, so all scroll-bars have to be controlled manually with the cursors, which is far from ideal...

By the way both these problems persist with last update (23.0.0.185). Are they known issues? Do you plan to fix them soon?

For now our work-around is to prevent flash plugin to update from 22 to 23 but this can only be a temporary solution, and it doesn't even work with all browsers (Safari doesn't allow out-of-date flash player).

Report · Oct 13, 2016

Hi,

Please log a bug in our bugbase https://bugbase.adobe.com/.

Thanks!

Report · Oct 13, 2016

The flex app is an internal application, I can't give access to it. So I have no substantial material to fill a bug report.

Report · Oct 13, 2016

Hi ,

You can attach the sample app ,which will help us to reproduce the issue at our end.

Report · Oct 13, 2016

Without a representative example to debug, there's not really much we can do. We have an extensive set of performance tests, and while we do intentionally favor security over performance, we haven't made changes recently that result in the kinds of egregious performance regression that you're describing, at least under normal circumstances.

While I totally believe that something is slower in your implementation, we're nowhere close to having an actionable amount of information. I *can* say that we're not hearing about new performance complaints (many of our major Flex enterprise customers with Enterprise agreements are very vocal and test regularly with our Beta releases).

Something has changed (we make several hundred changes in an average release) that seems to have an exaggerated impact in your specific application in your environment. We're certainly interested, but without any insight into what your client code is doing, there are an infeasibly large number of possibilities to pursue.

You have a couple options:

Take a look at your application using our performance profiler, Adobe Scout.

There's a good chance that you'll identify a hotspot in your code that presents an opportunity for significant optimization. At the very least, it should point you to the slow code, which will help you make a simplified example that you can share. If you're using an old Flex SDK, it may also point you to a Flex bug that was resolved in a newer release. Profiling is usually informative at the very least.
Submit a reduced example, or stand up a public-facing clone of the system (sans confidential data), so that we can access it for investigation purposes.
Engage Adobe in an Enterprise Support relationship explore the possibility of someone debugging the issue on-site

While you're investigating, you might also just look in your browser's developer tools to see if maybe the change is attributable to something there, like a new security constraint in the browser (which would probably show up in the Console), or some kind of network performance/connectivity issue that might be visible from the network tab.

Once you *do* have something for us to look at, please reply here with the associated bug number. I'll get an email notification automatically, and would be happy to assign it to an engineer for triage.

Thanks!