Hi, I forgot to mention that you should turn off all filters in the profiler so we can see global classes and the SDK classes.
But just from this information, you can see that there are 143 TextContainerManager.updateContainer calls. In new instances, measurement and layout can end up calling updateContainer, but that implies that there are 71 text widgets using TLF on the screen, or else something is causing more than one layout pass. I only see about 26 or so things that look like Labels that shouldn't be using TLF. Turning off the filters should show us how many layout passes there were, and how many UIComponents were instantiated. Often, folks are using creationPolicy="all" to save on development hassle and end up paying the price in performance. -Alex On 8/19/14 8:00 PM, "codekarma" <[email protected]> wrote: >Thanks for the response, here are the screenshots: > >profiler screenshot <http://imgur.com/QqzV7xo> >ui screenshot <http://imgur.com/OMvJu7t> > >(In order to make it more apparent all the items on the stage I did on the >TitleWindow setStyle("modalTransparency", 0); >setStyle("modalTransparencyBlur", 0); but profiler output is from after >that >so it doesn't impact the profiler numbers) > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/TitleWindow-severe-performa >nce-problem-15-sec-to-update-tp7677p7680.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
