You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Benoit Wiart (JIRA)" <ji...@apache.org> on 2013/11/11 22:46:18 UTC

[jira] [Updated] (FLEX-33893) CSSStyleDeclaration is inefficient during style matching

     [ https://issues.apache.org/jira/browse/FLEX-33893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Wiart updated FLEX-33893:
--------------------------------

    Attachment: cssstyledeclaration-example-1-mobile.png

> CSSStyleDeclaration is inefficient during style matching
> --------------------------------------------------------
>
>                 Key: FLEX-33893
>                 URL: https://issues.apache.org/jira/browse/FLEX-33893
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Mobile: Performance, Performance: Framework, Styles
>    Affects Versions: Apache Flex 4.11.0
>         Environment: desktop mobile
>            Reporter: Benoit Wiart
>              Labels: memory, performance
>         Attachments: cssstyledeclaration-example-1-mobile.png
>
>
> When no factory (or defaultFactory) is provided a new function is created when matching styles (addFactoryAndOverrideStylesToProtoChain, addStyleToProtoChain, applyFilter).
> This is a major source of unneeded memory allocations (== GC)
> The patch re-use a single function as the prototype is always reseted 
> This should be reviewed by an actionscript ninja ;-)



--
This message was sent by Atlassian JIRA
(v6.1#6144)