Flex Developed Flash Application Lags/Freezes

Question

My company has developed an internal Flex based Flash application that essentially displays a grid of data and allows the users to scroll left to right and up and down to view more column and row data. We've run into an issue with our new computers that when scrolling left to the right, the application lags greatly and then tends to freeze. We see the issue with Windows 10 on Lenovo X1 Carbon's and Surface Pro 4s that have high screen resolution/dpi. The issue does not occur with Windows 7 or Windows 10 on Dell's or other machine's with lower screen resolution. We are currently running Windows 10 1511 and have tried multiple versions of Flash player and Internet Explorer patches. We have also tried multiple display drivers to no avail.

When testing in Chrome, the issue does not occur.

Can anyone offer some guidance on why the application is behaving poorly on the high screen resolution/dpi computers?

Thanks.

jeromiec83223024 · Answer

Edge and "Modern IE" on Win8.1 and higher tend to have a default scale factor that isn't 1.0, so you get the double-whammy of a much larger set of pixels that need to be rendered, plus a bunch of additional computational overhead associated with handling the additional scaling work.

That said, I have a Surface Pro 4 sitting on my desk, and I haven't noticed anecdotally that we're having horrendous performance problems on Flex apps, and it does fine in all of our performance benchmarks.

My guess is that you're looking at a combination of some inefficient code or other CPU-intensive loop, compounded by the extra work going on for the high density displays.

The first thing I would recommend is taking a look at the application with the Adobe Scout performance profiler. It should give you a good idea of where the application is spending lots of time, and hopefully point you towards opportunities for optimization.

It's also worth mentioning that Adobe donated Flex to the Apache foundation a few years back, and you're probably using something that predates those machines by years. It could easily be something inefficient in the Flex framework that's fixed in a current version.

http://flex.apache.org/

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.