You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Colin Childs (JIRA)" <ji...@apache.org> on 2015/12/03 17:49:11 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15038070#comment-15038070 ]
Colin Childs commented on FLEX-33890:
-------------------------------------
I'd love to see this issue fixed. Any chance of this patch being applied soon?
> 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, patch, performance
> Attachments: 0001-gettypehierarchy-optimizations.patch, StyleProtoChain.as.patch, gettypehierarchy-example-1.png, gettypehierarchy-example-2.png, gettypehierarchy-example-3.png, gettypehierarchy-example-4.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.3.4#6332)