I spent hundreds of our developers on Adobe AIR Application with Flex 4.0, and now I thought I should finish, but after the application starts for more than a few hours, the user interface begins to lack ...
What I am doing: My application uses custom chromates, setting backgroundImages with transparency in BorderContainers inside Window modules. I open a lot of different pop-ups that are all based on Window-Class (not TitleWindow!), But are dynamically created and closed in ActionScript. Using Flex Profiler, I, of course, know that the garbage collector correctly destroys all allocated resources, and memory consumption does not increase with application downtime. Further, the profiler shows me that none of my methods take up extensive processor time, so this should also be good.
What is really interesting: If I constantly interact with the application (click buttons, text, ...) nothing happens, and everything is fine, BUT if I do not interact with the application for several minutes, and then come back - the reaction of the interface is very poor!
Really bad means that if I type in TextInput-Control, I can observe every letter written with a delay of at least 1 second!
Has anyone experienced a similar situation or someone who knows what the problem is? My suggestion is that after some activity, the flash player-runtime restricts the processor to use the AIR application and does not return full power when the user returns.
I tested the application using Flex 4.0, Flex 4.1, AIR 1.5, AIR 2.0 with Flash Player 9, as well as Flash Player 10 running on Windows XP and Windows 7 ...