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 11:51:20 UTC
[jira] [Updated] (FLEX-33890) Style engine : style matching
allocates a lot of memory even if everything is in cache
[ https://issues.apache.org/jira/browse/FLEX-33890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Wiart updated FLEX-33890:
--------------------------------
Attachment: gettypehierarchy-example-1.png
On the screenshots "de fermeture" should be translated to "closure" for those of you who don't have the chance to speak French.
the green dot highlight the unneeded allocations
> Style engine : style matching allocates a lot of memory even if everything is in cache
> --------------------------------------------------------------------------------------
>
> Key: FLEX-33890
> URL: https://issues.apache.org/jira/browse/FLEX-33890
> Project: Apache Flex
> Issue Type: Improvement
> Components: Mobile: Performance, Performance: Framework, Styles
> Affects Versions: Apache Flex 4.11.0
> Environment: mobile desktop
> Reporter: Benoit Wiart
> Labels: memory, performance
> Attachments: gettypehierarchy-example-1.png
>
>
> StyleProtoChain#getTypeHierarchy is called often and is responsible for a lot of unneeded memory allocations even if the type hierarchy is cached.
> This patch has 2 parts :
> - (1) : exception handling reworking in order to avoid the closure/activation creation by the try/catch
> - (2) : replace the use of a flash proxy with a custom class : It seems that the proxy was only used as an array.
--
This message was sent by Atlassian JIRA
(v6.1#6144)