Hi there, I’m having some really odd issues with FP10 + Air 1.x (currently 1.5 but it was just the same with 1.0)
First off, the really really strange thing.
My AIR app completely crashes not only with no error report, but even more, Flash (debug and non-debug mode) and Flex’s Profiler say everything is still running just fine.
So basically, the whole thing breaks down with no clear symptom (I’ve dissarmed and put together again the whole thing piece by piece and still no clear source of this behavior), no error report whatsoever…and actually, the hosts (FP10, Flex) say everything is AOK.
Still…the whole thing breaks down. I thought of an endless loop somewhere but not only did I triple checked every single loop in the whole source code, but also Flash will never come up with it’s typical “a script is taking too long, blah blah blah”.
Again, and I can’t stress this enough, Flash/Flex insist the whole thing is working great, 100% of it’s full potential…
That’s why I’m thinking that maybe, only maybe, this is a rendering issue (even though clicking on the AIR app when this happens makes WinXP go crazy about how unresponsive that app is), which leads me to…
Issue #2, really strange rendering / visual glitches.
It looks as if dirty rectangles where not working properly, or as if rendering is taking too long (even though the whole thing is running at 60fps constantly).
I’ll attach some screenshots, what you get to see there is basically a floating window frame, and you can see how the whole thing breaks down as if Photoshop’s rubber has been used to erase it, a flying thingy from the background went pass beneath, glitching those parts)
Anything moving seems to glitch one way or another, even more if I move one of this floating windows (for instance) around there’re these “render leaks”, as if it was taking too long to clean and update the screen, just like when Win is running really slow and you move a window and get windows pieces or borders ripped off and floating around 'till Win updates the screen as it’s supossed to do, the only thing is…again, it’s running at perfect 60FPS constantly.
Any thoughts on this ?
Except for my very own code, I’m only using the latest version of greensock’s tweening platform, more specifically TweenLite and TimelineLite only.
Thanks in advance for sharing thoughts and/or knowledge 
PS: one last thing, running on Flash CS4, deactivated WindowsBlinds (just in case it’s messing around with Flash), but still nothing, tryed it on a 100% clean XP installation, and still the same…
