An interesting read and I have encountered this type of problem before. However, in all the cases I have experienced this it always behaves the same, it's never been machine specific.
The problem only occurs on some machines, connecting to exactly the same appserver, serving up exactly the same SWF file, using exactly the same FlashPlayer. I think the IBM ILOG Elixir component is a red herring of sorts, it just happens to really show that it's lagging when interacting with bits using it. I've now got a developer environment up and running on a machine exhibiting the problem, so it's now easier to experiment around with it. Hooking up Scout with a proper telemetry enabled version of the product and experimenting with a part of the product on a screen which doesn't use the ILOG component I still get a constant 2-3% CPU time reported in internet explorer (a working machine reports 0%). Scout reports that 97% of the time is going into the Orange "Other" section in the rather unhelpful "Runtime Overhead" function. What does that mean? Hi Darren, I know your app isn't hung, but some of the principles described in [1] might apply. It is theoretically possible that an application gets into a situation where it is constantly trying to validate itself and thus the CPU never goes idle but the UI is operational. If I were in your shoes I would not worry about drag/drop and just see what AS is running when the app is "idle" but CPU is still running. HTH, -Alex [1] https://flexcloset.wordpress.com/2016/10/20/flex-app-hung/ -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Crippling-Lag-Windows-10-IE11-FlashPlayer-IBM-ILOG-Elixir-tp14958p14973.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
