I would first check what's going on in the Flash Professional project from which you created the component.
Do you have ActionScript code in Flash that fires many events or does heavy processing ?
Do you have vector graphics that contain many vectors ?
Another thing to point out is that you do not need to have one swc per component created with the Flex component kit for Flash. You can have several Flex components in a single swc created from Flash.
Thanks for the reply,
I have created all flex component used in my project in one swc only,Iam not using any actionscript code in flash that fires any event.
When i remove the skinning and check cpu usage will be zero ,so the problem is with stateful skinning.
After browsing i came to know that high cpu usage is because there appears to be an OnEnterFrame recursion on UIMovieClip, which is the Base Class for a stateful skin.
Kindly provide solutions for this issue.
Thanks and regards
1 person found this helpful
Patch UIMovieClip for Stateful Skins
A good practice for skinning components is to produce stateful vector skins in Flash and export them with the Flex Component Kit. All skins produced in this way use UIMovieClip as their base class, as described in the Design Spec. However, pre-Spark versions of UIMovieClip perform sizing calculations on every frame which causes an accumulation of CPU. For Flex 3.x projects, this can be avoided by extending UIMovieClip and removing the event handler, as described by Guillaume Malartre. A consequence of his approach is that some skinned components may need to be explicitly sized.