[
https://issues.apache.org/jira/browse/FLEX-33868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812657#comment-13812657
]
Benoit Wiart commented on FLEX-33868:
-------------------------------------
I don't have any suggestion :-(
We've set showBusyCursor to false on our remote operations
eg :
<remote:CustomRemoteObject id="remoteSecurityHelperRO"
destination="securityService" showBusyCursor="false"
requestTimeout="{ConfigRepository.TIMEOUT_IN_SECONDS}"
invoke="remoteObject_invokeHandler(event)"
result="remoteObject_resultHandler(event)"
fault="remoteObject_faultHandler(event)" />
Our scout profile showed that the cursor was created several times, I'll have a
look to see what's wrong there
> 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)
