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 08:50:17 GMT

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

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

My guess is that what happening is that you can only make a limited number of connections
at once (eg 4) and the sequence is a number of setBusy calls followed by the same number of
removeBusy and that occurs again and again - that could make lots of busy cursors.

I'll look further into remoteObject but roughly how many calls are you making? Can you look
at the calls in something like Charles reverse proxy (it understand and can decode AMF) to
see what is going on?

> 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
>            Priority: Minor
>              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