Mailing List
Home
Flash Pro
Extending Flash
Flash Macromedia Developer
Subjects
Firework Effect
setInterval bug identified and fixed
setInterval bug identified and fixed
ScrollPane component doesn 't auto update
Help: MX 2004 How to script a print button to print the entire sli
Event Dispatcher between classes
memory management removeMovieClip /
MX2004 Dataset itemClassName
Order of events per frame
XML to Object help
Textfield prototype question
Flash and QuickTime VR
Reading and displaying RSS feeds in Flash MX
Flash MX 2004 Sucks
AW: [Flashcoders] Switch/Case vs If/else
AW: [Flashcoders] Switch/Case vs If/else
Flash Interface with 10mb xml file
Web Service Results
Listener Object 's best practice
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
memory management - removeMovieClip /

memory management - removeMovieClip /

2004-02-21       - By Philip Double

 Back
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

I am very interested in this subject. I am working on a very large -
completely dynamic flapplication right now. I have not run into issues
with memory yet, but worry that as it grows larger that I will. I am
loading and unloading literally thousands of movieClips and hundreds of
external .swfs.

I had no idea that the internal pieces of a movieClip would stay in
memory once the MC itself was unloaded. Would you be interested in
working out an extend of the MovieClip Class to take care of this?

phil double


On Feb 21, 2004, at 2:00 PM, Lindsey Simon wrote:

> delete
> Reply-To:
> In-Reply-To: <200402190939218.SM01784@(protected) >
> X-OS: Linux chiefy 2.4.23
> X-mailer: Mutt 1.5.5.1+cvs20040105i (2003-11-05)
>
> I really would love to see some more dialogue on this subject.
>
> One thing I 've found is that even with unloadMove and removeMovieClip,
> there are still pointers recursively existing for the object following
> those methods. Which makes me think they 're still in memory and
> thereby sucking. So, before I removeMovieClip I recurse through the
> object and remove movie clips, text fields, and then use delete on the
> references. I use a few prototypes I wrote to do this and I think
> they 're ugly, but I believe they are working.
>
> Does anyone else want to share their wisdom on this - I 'd like to come
> up with a nice function to completely obliterate a movie clip and all
> of it 's functions, textfields, properties, etc.. recursively. i.e. for
> it 's children.
>
> I don 't want to burden the list with a huge bunch of code unless this
> topic is of interest to others.
> -l
>
>
>
> =-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
> Supported by Fig Leaf Software
> =-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
> Be sure to check the archives and the wiki:
> http://chattyfig.figleaf.com/
> =-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
> http://chattyfig.figleaf.com/cgi-bin/ezmlm-cgi?1:mss:104901
> =-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
> To unsubscribe send a blank e-mail to:
> Normal Mode: flashcoders-unsubscribe@(protected)
> Digest Mode: flashcoders-digest-unsubscrive@(protected)
>


=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Supported by Fig Leaf Software
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Be sure to check the archives and the wiki:
http://chattyfig.figleaf.com/
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
http://chattyfig.figleaf.com/cgi-bin/ezmlm-cgi?1:mss:104903
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
To unsubscribe send a blank e-mail to:
Normal Mode: flashcoders-unsubscribe@(protected)
Digest Mode: flashcoders-digest-unsubscrive@(protected)