Custom Chrome Performance in AIR 1.0.1
May 8th, 2008
I had an AIR application that I was developing for a client around the time AIR 1.0 was released. This was a custom chrome application. When I profiled and tested the application I was less than impressed with the processor utilization. Actually, I was less than impressed with the processor utilization of any of the application I build that had system chrome set to NONE and had transparency. So, image my surprise when I did some more profiling and testing on this application (now that I am running AIR 1.0.1) to see that this issue was mostly gone.
I tried to find the actual release notes for AIR 1.0.1 to see if this was one of the issues that was addressed, but I couldn’t find any specifics (the release notes didn’t give any specifics). In all honesty, this improvement could be due to an external factor, but it appears to me that is was a fix that actually came with 1.0.1. Custom chrome applications (while not always a great decision) are now a more viable solution since this resource utilization issue has apparently been remedied.
|
Comments
| Trackback |
Del.icio.us |
Digg |
Technorati
2 comments on “Custom Chrome Performance in AIR 1.0.1”
01
I am still having this problem in my custom chrome app but it only reveals itself when transparency if set to false. When transparency is false the app becomes a CPU hog.
02
@Cervantes - Interesting…It looks as though they might have just target the transparency=true issue with AIR 1.0.1. Hopefully they can address yours for the next update.
Leave a Reply