flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33868) CursorManagerImpl#setBusyCursor is memory inefficient
Date Mon, 04 Nov 2013 06:43:18 GMT

    [ https://issues.apache.org/jira/browse/FLEX-33868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812641#comment-13812641
] 

Justin Mclean commented on FLEX-33868:
--------------------------------------

>From a quick look at the Cursor manger code, a new cursor is not created (see the item.cursorID
!= currentCursorID check in showCurrentCursor), however it does add information about the
new cursor to the busyCursorList, this is because it's possible to have multiple different
busy cursors (perhaps different ones for different priorities?) or the busy cursor style could
be changed. Both seem unlikely use cases to me, so any suggestion how to improve this?

> CursorManagerImpl#setBusyCursor is memory inefficient
> -----------------------------------------------------
>
>                 Key: FLEX-33868
>                 URL: https://issues.apache.org/jira/browse/FLEX-33868
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Mobile: Performance, Performance: Framework
>    Affects Versions: Apache Flex 4.11.0
>         Environment: mobile
>            Reporter: Benoit Wiart
>              Labels: memory, performance
>         Attachments: busycursor.png
>
>
> Each time CursorManagerImpl#setBusyCursor is called a new cursor is created.
> setBusyCursor may be called on each remote invocation



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

Mime
View raw message