flex-issues mailing list archives

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

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

Benoit Wiart commented on FLEX-33868:

> I assume CustomRemoteObject just extends RemoteObject?
Yes and we have several RemoteObject

my initial comment was probably misleading.
you should read
Each time CursorManagerImpl#setBusyCursor is called *in a remote operation* a new cursor is
I don't know if it's possible to keep and reuse the constructed Cursor

If not then close the bug : there is a workaround with showBusyCursor="false" 

I'll upload some scout screenshots

> 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

View raw message