LiveDocs Comments - flash - 9.0 - main - 00000139.html

flash/9.0/main/00000139.html

Ryan Phelan — 2008-09-23T17:25:57

You shouldn't have to tell the garbage collector to destroy something, if you build your application correctly everything that should get destroyed eventually does.

That being said, the FLVPlayback component has a horrible memory leak problem that needs to be fixed. It should have a dispose() function that frees up any resources that it is using (Timers, EventListeners, and NetConnections).

I posted a workaround on my site: http://www.rphelan.com/2008/09/22/flvplayback-memory-leak-fixed/

flash/9.0/main/00000139.html

2008-07-22T08:21:41

I guess this makes sense in some strange way to keep objects in memory that have subscribed to an event. But if this is the case, there should be a method for Overriding this for the Garbage Collector. Or expose some of the internal Events of the Components that are presented by Flash more easily available to removeEventListener.

example showing the Memory Leak Problem:
Dude go drag an FLVPlayback Component onto the stage and have it play and FLV-----THEN remove the FLVPlayback component with a button---------The video keeps Playing the back ground ------THIS is due to exactly what this article is saying---

Why shouldn't we be able to say :

Garbage collector.destroy(FLVPlayback component);----RESULTING in the death of the FLVPlayback component in everyway including the destruction of it's events, the Stream, the displayObject

For those of us who dont' want to build nor have the time to Build custom Media Player components, this is a big problem....

flash/9.0/main/00000139.html

ElliotRock — 2008-07-20T03:44:38

The first example gives substandard instructions.

Is the package part of the class an external .as file? If so what is it called.

This example doesn't work inside flash CS3 Pro. It gives a "1037: Packages cannot be nested" error. I assumed it could just be pasted into the first frame.

Please fix and expand the instructions to include any UI steps.

Thanks

flash/9.0/main/00000139.html

PGunderson — 2008-02-27T17:15:37

yes

flash/9.0/main/00000139.html

IceCo — 2007-08-22T17:20:52

"One important consequence of this parameter involves working with display objects' events. Normally, you might expect a display object to be removed from memory when it is removed from the display list. However, if other objects have subscribed as listeners to that display object, with the useWeakReference parameter set to false (the default), the display object will continue to exist in Flash Player's memory even though it no longer appears on the screen. To work around this issue, either have all the listeners subscribe to the display object with the useWeakReference parameter set to true, or else remove all the event listeners from the display object using the removeEventListener() method."

This does not make sense. There are two roles here: 1) the event dispatcher and 2) the event listener.

According to the above excerpt, an event dispatcher will never be garbage collected as long as it has other objects listening to it. Is this true?