RemoteObject still causes memory leak !!
I reported about this at Flex 3.2.
To use and discard RemoteObject causes memory leak.
You know, it's deferred...
So, I tested this at Flex 4 (revision 13101).
It still causes memory leak !!
I guess "deferred" status has the risk called "forgot".
I reported this again.
To use and discard RemoteObject causes memory leak at Flex 4.
Please fix this, Adobe!!
To use and discard RemoteObject causes memory leak.
You know, it's deferred...
So, I tested this at Flex 4 (revision 13101).
It still causes memory leak !!
I guess "deferred" status has the risk called "forgot".
I reported this again.
To use and discard RemoteObject causes memory leak at Flex 4.
Please fix this, Adobe!!
Comments (2)
Looking for a job
Job request is from here
-
Flex3/AIR adviser
Making technical documents and samples of Flex3/AIR for you.
-
Contract development
Developing Flex3/4, AIR application.
-
Flex3/AIR consulting
Consulting for the company which wants to build Flex2/AIR application.
I found memory leak in the NetConnection object, as RemoteObject relies on NetConnection maybe this is the same problem.
But as i read your workaround and the comment below, it seems that if you reuse the same object you do not have memory leak again, could you confirm that ? With the NetConnection the problem exists with or without reuse (on linux, doesn't test on windows for the moment).
http://bugs.adobe.com/jira/browse/SDK-24820