[
https://issues.apache.org/jira/browse/FLEX-33868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812643#comment-13812643
]
Justin Mclean commented on FLEX-33868:
--------------------------------------
Sample program:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009";
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"
creationComplete="setBusy(event)">
<fx:Script>
<![CDATA[
import mx.events.FlexEvent;
import mx.managers.CursorManager;
protected function setBusy(event:FlexEvent):void
{
CursorManager.setBusyCursor();
CursorManager.setBusyCursor();
CursorManager.setBusyCursor();
CursorManager.removeBusyCursor()
CursorManager.removeBusyCursor();
CursorManager.removeBusyCursor();
}
]]>
</fx:Script>
</s:Application>
If you put a break point on the BusyCursor constructor it's only called once.
> 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)
