AFAIK, they do not cause leaks. If you show some data or a simple test case
that indicates that they are, I will try to take a look.
On 8/30/10 8:36 AM, "lew.miller" wrote:
I've been wrestling with memory leaks and the FB4 profiler and lately have been
trying to understand activation-objects and their relationship to GC because
the vast majority (often all) of the references the profiler tells me an object
has keeping it in memory come from activation objects.
While researching this I came across a note from Alex Harui saying "I've never
seen an activation object cause a leak" but other things I've read seem to
suggest they can. (Certainly the profiler would lead me to believe it.) Can
anybody enlighten me? Or just point me to the place to read documentation on
the subject that is up-to-date? Half of what I've read about activation
objects appears to be from earlier versions of ActionScript so I'm not sure
what to believe.
If an activation object can cause a memory leak, I'd like to understand how. I
may not have a firm grasp of the lifecycle of an activation object but I
thought it would no longer be accessible from the GC root after the function
it's created for finishes executing.
Any help or pointers would be greatly appreciated.
Lew
--
Alex Harui
Flex SDK Team
Adobe System, Inc.
http://blogs.adobe.com/aharui
