You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Oleg Sivokon (Commented) (JIRA)" <ji...@apache.org> on 2012/03/09 10:00:56 UTC

[jira] [Commented] (FLEX-27) When flex debug ,warning Memory Leak message

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

Oleg Sivokon commented on FLEX-27:
----------------------------------

Maybe it would be just better to discourage people from using [RemoteClass] meta? It was a bad idea to use it in the first place anyway.

If it isn't obvious why RemoteClass is a bad idea: first of all, it's only slightly more verbose than registerClassAlias, so it's a very small gain in terms of convenience. On the other hand, when you use registerClassAlias you can surely tell who and when registered the alias. You don't always want it to happen at the application start, also, you may want the code registering the alias to be loaded later. You don't have these options with RemoteClass. I think people used it because it was in all kinds of tutorials etc, never giving it a critical judgment. Finally, RemoteClass created quite a bit of confusion with it's counterpart. Some results of this confusion were these: people tried to use it in the library code to no effect, obviously.
                
> When flex debug ,warning Memory Leak message
> --------------------------------------------
>
>                 Key: FLEX-27
>                 URL: https://issues.apache.org/jira/browse/FLEX-27
>             Project: Apache Flex
>          Issue Type: Bug
>         Environment: Flex SDK 4.6.0.23201B   Flash Builder4.5 Flash Player11.x
>            Reporter: hanjn
>            Assignee: Bertrand Delacretaz
>
> look this bug  detail at   https://bugs.adobe.com/jira/browse/SDK-30550   。
> adobe say this bug is  fix with 22831 ,The problem occurs in the latest version of the sdk

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira