Re: [FlashCoders] Images stay on memory forever?
eric dolecki schrieb:
to remove a movieclip, you need to create or attach it first. if you're
using the IDE to place the mcs, you can't use removeMovieClip().
that is not totally true:
you could always:
var mc = _root.createEmptyMovieClip('___dummy', _root.getNextHighestDepth());
mc_onStage.swapDepths(mc);
mc_onStage.removeMovieClip();
micha
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
This is the only code I've got:
n = 1;
btn.onRelease = function():Void {
_root["p"+n].swapDepths(1);
_root["p"+n].removeMovieClip();
n++;
}
I left it open for 15 minutes. Doesn't free memory...
Tested with Xray too. Nothing is left on stage except for the button.
Dimitiros
- Original Message -
From: "eric dolecki" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list"
Sent: Thursday, August 31, 2006 9:28 PM
Subject: Re: [FlashCoders] Images stay on memory forever?
remove all references to the mc in code & see what happens. might not be
immediate. could take a few minutes.
On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote:
Of course I'm swapping depths before I remove it.
I see it removed, but the memory doesn't free
Dimitrios
- Original Message -
From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list"
Sent: Thursday, August 31, 2006 9:09 PM
Subject: RE: [FlashCoders] Images stay on memory forever?
That is correct. If you want to remove a movieclip that you did not
attach using attachMovie (one that is manually there on a layer in the
timeline at compile) then you have to first swapDepths() it and then you
can removeMovieClip it.
BLITZ | Steven Sacks - 310-551-0200 x209
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:flashcoders-
> [EMAIL PROTECTED] On Behalf Of eric dolecki
> Sent: Thursday, August 31, 2006 10:52 AM
> To: Flashcoders mailing list
> Subject: Re: [FlashCoders] Images stay on memory forever?
>
> to remove a movieclip, you need to create or attach it first. if
you're
> using the IDE to place the mcs, you can't use removeMovieClip().
>
> if a mc is not on stage, is invisible, it will still be rendered by
the
> player.
>
> Thats the way it works, whether it makes sense to you or not.
>
> On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote:
> >
> > Hi Steven,
> >
> > Thanks for the information.
> > I've read this great article before, I'll read it once more
> > to refresh my memory.
> >
> > My mistake, I forgot to mention that I have the same issue
> > even if I remove the movieclip with removeMovieClip(),
> > or move it to negative coords, outside the visible stage area.
> >
> > Does this still make sense? Well, not to me!
> >
> > Dimitrios
> >
> >
> >
> > - Original Message -
> > From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]>
> > To: "Flashcoders mailing list"
> > Sent: Thursday, August 31, 2006 8:32 PM
> > Subject: RE: [FlashCoders] Images stay on memory forever?
> >
> >
> > Setting a movieclip to invisible doesn't free up memory, nor does it
> > reduce processing power that anything in that clip is doing. The
only
> > thing it frees up is drawing power, which can help in some cases.
> >
> > The Flash garbage collector is not as good as it could be and we
> > currently don't have any hooks into it. It's very easy for memory
waste
> > (as opposed to a leak) to occur when one isn't sure how it happens.
> >
> > Here is a great article on Scope Chain and Memory Waste. Recommended
> > reading for anyone interested in memory management in Flash.
> > http://timotheegroleau.com/Flash/articles/scope_chain.htm
> >
> > That being said, back in the Director days clients used to freak out
> > because Director used 99% of the CPU. What they didn't understand
was
> > that it would readily give up any of its processing power when
anything
> > else needed it, but as long as it was running, it used as much
available
> > CPU as it could to ensure it ran as smoothly as possible. If your
> > client is giving you a hard time over a few thousand k of memory
usage,
> > your project is going too well. Slow it down and miss some
milestones.
> > Give them something important to pester you about. ;)
> >
> > HTH!
> > ___
> > Flashcoders@chattyfig.figleaf.com
> > To change your subscription options or search the archive:
> > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
> >
> > Brought to you by Fig Leaf Software
> > Premier Authorized Adobe Consulting and Training
> > http://www.figleaf.com
> > http://training.figleaf.com
> >
> >
> >
> > ___
> > Flashcoders@chattyfig.figleaf.com
> > To change your subscription options or search the archive:
> > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
> >
> > Bro
Re: [FlashCoders] Images stay on memory forever?
remove all references to the mc in code & see what happens. might not be immediate. could take a few minutes. On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: Of course I'm swapping depths before I remove it. I see it removed, but the memory doesn't free Dimitrios - Original Message - From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 9:09 PM Subject: RE: [FlashCoders] Images stay on memory forever? That is correct. If you want to remove a movieclip that you did not attach using attachMovie (one that is manually there on a layer in the timeline at compile) then you have to first swapDepths() it and then you can removeMovieClip it. BLITZ | Steven Sacks - 310-551-0200 x209 > -Original Message- > From: [EMAIL PROTECTED] [mailto:flashcoders- > [EMAIL PROTECTED] On Behalf Of eric dolecki > Sent: Thursday, August 31, 2006 10:52 AM > To: Flashcoders mailing list > Subject: Re: [FlashCoders] Images stay on memory forever? > > to remove a movieclip, you need to create or attach it first. if you're > using the IDE to place the mcs, you can't use removeMovieClip(). > > if a mc is not on stage, is invisible, it will still be rendered by the > player. > > Thats the way it works, whether it makes sense to you or not. > > On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: > > > > Hi Steven, > > > > Thanks for the information. > > I've read this great article before, I'll read it once more > > to refresh my memory. > > > > My mistake, I forgot to mention that I have the same issue > > even if I remove the movieclip with removeMovieClip(), > > or move it to negative coords, outside the visible stage area. > > > > Does this still make sense? Well, not to me! > > > > Dimitrios > > > > > > > > - Original Message - > > From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> > > To: "Flashcoders mailing list" > > Sent: Thursday, August 31, 2006 8:32 PM > > Subject: RE: [FlashCoders] Images stay on memory forever? > > > > > > Setting a movieclip to invisible doesn't free up memory, nor does it > > reduce processing power that anything in that clip is doing. The only > > thing it frees up is drawing power, which can help in some cases. > > > > The Flash garbage collector is not as good as it could be and we > > currently don't have any hooks into it. It's very easy for memory waste > > (as opposed to a leak) to occur when one isn't sure how it happens. > > > > Here is a great article on Scope Chain and Memory Waste. Recommended > > reading for anyone interested in memory management in Flash. > > http://timotheegroleau.com/Flash/articles/scope_chain.htm > > > > That being said, back in the Director days clients used to freak out > > because Director used 99% of the CPU. What they didn't understand was > > that it would readily give up any of its processing power when anything > > else needed it, but as long as it was running, it used as much available > > CPU as it could to ensure it ran as smoothly as possible. If your > > client is giving you a hard time over a few thousand k of memory usage, > > your project is going too well. Slow it down and miss some milestones. > > Give them something important to pester you about. ;) > > > > HTH! > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > > > > > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > ___ > Flashcoders@chattyfig.figleaf.com > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figle
Re: [FlashCoders] Images stay on memory forever?
On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: Of course I'm swapping depths before I remove it. I see it removed, but the memory doesn't free Dimitrios - Original Message - From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 9:09 PM Subject: RE: [FlashCoders] Images stay on memory forever? That is correct. If you want to remove a movieclip that you did not attach using attachMovie (one that is manually there on a layer in the timeline at compile) then you have to first swapDepths() it and then you can removeMovieClip it. BLITZ | Steven Sacks - 310-551-0200 x209 > -Original Message- > From: [EMAIL PROTECTED] [mailto:flashcoders- > [EMAIL PROTECTED] On Behalf Of eric dolecki > Sent: Thursday, August 31, 2006 10:52 AM > To: Flashcoders mailing list > Subject: Re: [FlashCoders] Images stay on memory forever? > > to remove a movieclip, you need to create or attach it first. if you're > using the IDE to place the mcs, you can't use removeMovieClip(). > > if a mc is not on stage, is invisible, it will still be rendered by the > player. > > Thats the way it works, whether it makes sense to you or not. > > On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: > > > > Hi Steven, > > > > Thanks for the information. > > I've read this great article before, I'll read it once more > > to refresh my memory. > > > > My mistake, I forgot to mention that I have the same issue > > even if I remove the movieclip with removeMovieClip(), > > or move it to negative coords, outside the visible stage area. > > > > Does this still make sense? Well, not to me! > > > > Dimitrios > > > > > > > > - Original Message - > > From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> > > To: "Flashcoders mailing list" > > Sent: Thursday, August 31, 2006 8:32 PM > > Subject: RE: [FlashCoders] Images stay on memory forever? > > > > > > Setting a movieclip to invisible doesn't free up memory, nor does it > > reduce processing power that anything in that clip is doing. The only > > thing it frees up is drawing power, which can help in some cases. > > > > The Flash garbage collector is not as good as it could be and we > > currently don't have any hooks into it. It's very easy for memory waste > > (as opposed to a leak) to occur when one isn't sure how it happens. > > > > Here is a great article on Scope Chain and Memory Waste. Recommended > > reading for anyone interested in memory management in Flash. > > http://timotheegroleau.com/Flash/articles/scope_chain.htm > > > > That being said, back in the Director days clients used to freak out > > because Director used 99% of the CPU. What they didn't understand was > > that it would readily give up any of its processing power when anything > > else needed it, but as long as it was running, it used as much available > > CPU as it could to ensure it ran as smoothly as possible. If your > > client is giving you a hard time over a few thousand k of memory usage, > > your project is going too well. Slow it down and miss some milestones. > > Give them something important to pester you about. ;) > > > > HTH! > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > > > > > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > ___ > Flashcoders@chattyfig.figleaf.com > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com ___ Flashcoders@chattyfig.fi
Re: [FlashCoders] Images stay on memory forever?
Of course I'm swapping depths before I remove it. I see it removed, but the memory doesn't free Even if you found the correct method (if this wasn't), I believe that you're still dealing with garbage collection, which clears memory for dead (soft, luke-warm, whatever) references when, and if, it ever decides to! Scott On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: Of course I'm swapping depths before I remove it. I see it removed, but the memory doesn't free Dimitrios - Original Message - From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 9:09 PM Subject: RE: [FlashCoders] Images stay on memory forever? That is correct. If you want to remove a movieclip that you did not attach using attachMovie (one that is manually there on a layer in the timeline at compile) then you have to first swapDepths() it and then you can removeMovieClip it. BLITZ | Steven Sacks - 310-551-0200 x209 > -Original Message- > From: [EMAIL PROTECTED] [mailto:flashcoders- > [EMAIL PROTECTED] On Behalf Of eric dolecki > Sent: Thursday, August 31, 2006 10:52 AM > To: Flashcoders mailing list > Subject: Re: [FlashCoders] Images stay on memory forever? > > to remove a movieclip, you need to create or attach it first. if you're > using the IDE to place the mcs, you can't use removeMovieClip(). > > if a mc is not on stage, is invisible, it will still be rendered by the > player. > > Thats the way it works, whether it makes sense to you or not. > > On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: > > > > Hi Steven, > > > > Thanks for the information. > > I've read this great article before, I'll read it once more > > to refresh my memory. > > > > My mistake, I forgot to mention that I have the same issue > > even if I remove the movieclip with removeMovieClip(), > > or move it to negative coords, outside the visible stage area. > > > > Does this still make sense? Well, not to me! > > > > Dimitrios > > > > > > > > - Original Message - > > From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> > > To: "Flashcoders mailing list" > > Sent: Thursday, August 31, 2006 8:32 PM > > Subject: RE: [FlashCoders] Images stay on memory forever? > > > > > > Setting a movieclip to invisible doesn't free up memory, nor does it > > reduce processing power that anything in that clip is doing. The only > > thing it frees up is drawing power, which can help in some cases. > > > > The Flash garbage collector is not as good as it could be and we > > currently don't have any hooks into it. It's very easy for memory waste > > (as opposed to a leak) to occur when one isn't sure how it happens. > > > > Here is a great article on Scope Chain and Memory Waste. Recommended > > reading for anyone interested in memory management in Flash. > > http://timotheegroleau.com/Flash/articles/scope_chain.htm > > > > That being said, back in the Director days clients used to freak out > > because Director used 99% of the CPU. What they didn't understand was > > that it would readily give up any of its processing power when anything > > else needed it, but as long as it was running, it used as much available > > CPU as it could to ensure it ran as smoothly as possible. If your > > client is giving you a hard time over a few thousand k of memory usage, > > your project is going too well. Slow it down and miss some milestones. > > Give them something important to pester you about. ;) > > > > HTH! > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > > > > > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > ___ > Flashcoders@chattyfig.figleaf.com &
Re: [FlashCoders] Images stay on memory forever?
Of course I'm swapping depths before I remove it. I see it removed, but the memory doesn't free Dimitrios - Original Message - From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 9:09 PM Subject: RE: [FlashCoders] Images stay on memory forever? That is correct. If you want to remove a movieclip that you did not attach using attachMovie (one that is manually there on a layer in the timeline at compile) then you have to first swapDepths() it and then you can removeMovieClip it. BLITZ | Steven Sacks - 310-551-0200 x209 -Original Message- From: [EMAIL PROTECTED] [mailto:flashcoders- [EMAIL PROTECTED] On Behalf Of eric dolecki Sent: Thursday, August 31, 2006 10:52 AM To: Flashcoders mailing list Subject: Re: [FlashCoders] Images stay on memory forever? to remove a movieclip, you need to create or attach it first. if you're using the IDE to place the mcs, you can't use removeMovieClip(). if a mc is not on stage, is invisible, it will still be rendered by the player. Thats the way it works, whether it makes sense to you or not. On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: > > Hi Steven, > > Thanks for the information. > I've read this great article before, I'll read it once more > to refresh my memory. > > My mistake, I forgot to mention that I have the same issue > even if I remove the movieclip with removeMovieClip(), > or move it to negative coords, outside the visible stage area. > > Does this still make sense? Well, not to me! > > Dimitrios > > > > - Original Message - > From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> > To: "Flashcoders mailing list" > Sent: Thursday, August 31, 2006 8:32 PM > Subject: RE: [FlashCoders] Images stay on memory forever? > > > Setting a movieclip to invisible doesn't free up memory, nor does it > reduce processing power that anything in that clip is doing. The only > thing it frees up is drawing power, which can help in some cases. > > The Flash garbage collector is not as good as it could be and we > currently don't have any hooks into it. It's very easy for memory waste > (as opposed to a leak) to occur when one isn't sure how it happens. > > Here is a great article on Scope Chain and Memory Waste. Recommended > reading for anyone interested in memory management in Flash. > http://timotheegroleau.com/Flash/articles/scope_chain.htm > > That being said, back in the Director days clients used to freak out > because Director used 99% of the CPU. What they didn't understand was > that it would readily give up any of its processing power when anything > else needed it, but as long as it was running, it used as much available > CPU as it could to ensure it ran as smoothly as possible. If your > client is giving you a hard time over a few thousand k of memory usage, > your project is going too well. Slow it down and miss some milestones. > Give them something important to pester you about. ;) > > HTH! > ___ > Flashcoders@chattyfig.figleaf.com > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com > > > > ___ > Flashcoders@chattyfig.figleaf.com > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com > ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
RE: [FlashCoders] Images stay on memory forever?
That is correct. If you want to remove a movieclip that you did not attach using attachMovie (one that is manually there on a layer in the timeline at compile) then you have to first swapDepths() it and then you can removeMovieClip it. BLITZ | Steven Sacks - 310-551-0200 x209 > -Original Message- > From: [EMAIL PROTECTED] [mailto:flashcoders- > [EMAIL PROTECTED] On Behalf Of eric dolecki > Sent: Thursday, August 31, 2006 10:52 AM > To: Flashcoders mailing list > Subject: Re: [FlashCoders] Images stay on memory forever? > > to remove a movieclip, you need to create or attach it first. if you're > using the IDE to place the mcs, you can't use removeMovieClip(). > > if a mc is not on stage, is invisible, it will still be rendered by the > player. > > Thats the way it works, whether it makes sense to you or not. > > On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: > > > > Hi Steven, > > > > Thanks for the information. > > I've read this great article before, I'll read it once more > > to refresh my memory. > > > > My mistake, I forgot to mention that I have the same issue > > even if I remove the movieclip with removeMovieClip(), > > or move it to negative coords, outside the visible stage area. > > > > Does this still make sense? Well, not to me! > > > > Dimitrios > > > > > > > > - Original Message ----- > > From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> > > To: "Flashcoders mailing list" > > Sent: Thursday, August 31, 2006 8:32 PM > > Subject: RE: [FlashCoders] Images stay on memory forever? > > > > > > Setting a movieclip to invisible doesn't free up memory, nor does it > > reduce processing power that anything in that clip is doing. The only > > thing it frees up is drawing power, which can help in some cases. > > > > The Flash garbage collector is not as good as it could be and we > > currently don't have any hooks into it. It's very easy for memory waste > > (as opposed to a leak) to occur when one isn't sure how it happens. > > > > Here is a great article on Scope Chain and Memory Waste. Recommended > > reading for anyone interested in memory management in Flash. > > http://timotheegroleau.com/Flash/articles/scope_chain.htm > > > > That being said, back in the Director days clients used to freak out > > because Director used 99% of the CPU. What they didn't understand was > > that it would readily give up any of its processing power when anything > > else needed it, but as long as it was running, it used as much available > > CPU as it could to ensure it ran as smoothly as possible. If your > > client is giving you a hard time over a few thousand k of memory usage, > > your project is going too well. Slow it down and miss some milestones. > > Give them something important to pester you about. ;) > > > > HTH! > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > > > > > > ___ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > ___ > Flashcoders@chattyfig.figleaf.com > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
to remove a movieclip, you need to create or attach it first. if you're using the IDE to place the mcs, you can't use removeMovieClip(). if a mc is not on stage, is invisible, it will still be rendered by the player. Thats the way it works, whether it makes sense to you or not. On 8/31/06, Dimitrios Bendilas <[EMAIL PROTECTED]> wrote: Hi Steven, Thanks for the information. I've read this great article before, I'll read it once more to refresh my memory. My mistake, I forgot to mention that I have the same issue even if I remove the movieclip with removeMovieClip(), or move it to negative coords, outside the visible stage area. Does this still make sense? Well, not to me! Dimitrios - Original Message - From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 8:32 PM Subject: RE: [FlashCoders] Images stay on memory forever? Setting a movieclip to invisible doesn't free up memory, nor does it reduce processing power that anything in that clip is doing. The only thing it frees up is drawing power, which can help in some cases. The Flash garbage collector is not as good as it could be and we currently don't have any hooks into it. It's very easy for memory waste (as opposed to a leak) to occur when one isn't sure how it happens. Here is a great article on Scope Chain and Memory Waste. Recommended reading for anyone interested in memory management in Flash. http://timotheegroleau.com/Flash/articles/scope_chain.htm That being said, back in the Director days clients used to freak out because Director used 99% of the CPU. What they didn't understand was that it would readily give up any of its processing power when anything else needed it, but as long as it was running, it used as much available CPU as it could to ensure it ran as smoothly as possible. If your client is giving you a hard time over a few thousand k of memory usage, your project is going too well. Slow it down and miss some milestones. Give them something important to pester you about. ;) HTH! ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
Hi Steven, Thanks for the information. I've read this great article before, I'll read it once more to refresh my memory. My mistake, I forgot to mention that I have the same issue even if I remove the movieclip with removeMovieClip(), or move it to negative coords, outside the visible stage area. Does this still make sense? Well, not to me! Dimitrios - Original Message - From: "Steven Sacks | BLITZ" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 8:32 PM Subject: RE: [FlashCoders] Images stay on memory forever? Setting a movieclip to invisible doesn't free up memory, nor does it reduce processing power that anything in that clip is doing. The only thing it frees up is drawing power, which can help in some cases. The Flash garbage collector is not as good as it could be and we currently don't have any hooks into it. It's very easy for memory waste (as opposed to a leak) to occur when one isn't sure how it happens. Here is a great article on Scope Chain and Memory Waste. Recommended reading for anyone interested in memory management in Flash. http://timotheegroleau.com/Flash/articles/scope_chain.htm That being said, back in the Director days clients used to freak out because Director used 99% of the CPU. What they didn't understand was that it would readily give up any of its processing power when anything else needed it, but as long as it was running, it used as much available CPU as it could to ensure it ran as smoothly as possible. If your client is giving you a hard time over a few thousand k of memory usage, your project is going too well. Slow it down and miss some milestones. Give them something important to pester you about. ;) HTH! ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
RE: [FlashCoders] Images stay on memory forever?
Setting a movieclip to invisible doesn't free up memory, nor does it reduce processing power that anything in that clip is doing. The only thing it frees up is drawing power, which can help in some cases. The Flash garbage collector is not as good as it could be and we currently don't have any hooks into it. It's very easy for memory waste (as opposed to a leak) to occur when one isn't sure how it happens. Here is a great article on Scope Chain and Memory Waste. Recommended reading for anyone interested in memory management in Flash. http://timotheegroleau.com/Flash/articles/scope_chain.htm That being said, back in the Director days clients used to freak out because Director used 99% of the CPU. What they didn't understand was that it would readily give up any of its processing power when anything else needed it, but as long as it was running, it used as much available CPU as it could to ensure it ran as smoothly as possible. If your client is giving you a hard time over a few thousand k of memory usage, your project is going too well. Slow it down and miss some milestones. Give them something important to pester you about. ;) HTH! ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
Well, this is a test applicaiton. The actual application I need this teset for is a game that starts with 70MBs on memory and soon builds up to 100MBs. And then the performance slows down substantially. I've been doing tests for weeks and I'm 99% there is nothing wrong with my code, it seems that it's the images that build up the memory. These particular clips in my example are not created with attachMovie, they are on stage from the beginning, but my game is using only attachMovie. Thanks, Dimitrios - Original Message - From: "Martin Wood" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 8:17 PM Subject: Re: [FlashCoders] Images stay on memory forever? are the clips created via attachMovie? why do you need to reclaim 4MB? its not a lot of memory. Flash may well use a memory management strategy that doesnt require it to immediately return the memory its allocated. Dimitrios Bendilas wrote: Hi Martin, Ok, but the memory doesn't even free if I remove the movie clip with .removeMovieClip() And I tried moving it out of the stage as well... Dimitrios ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
are the clips created via attachMovie? why do you need to reclaim 4MB? its not a lot of memory. Flash may well use a memory management strategy that doesnt require it to immediately return the memory its allocated. Dimitrios Bendilas wrote: Hi Martin, Ok, but the memory doesn't even free if I remove the movie clip with .removeMovieClip() And I tried moving it out of the stage as well... Dimitrios ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
Hi Martin, Ok, but the memory doesn't even free if I remove the movie clip with .removeMovieClip() And I tried moving it out of the stage as well... Dimitrios - Original Message - From: "Martin Wood" <[EMAIL PROTECTED]> To: "Flashcoders mailing list" Sent: Thursday, August 31, 2006 7:53 PM Subject: Re: [FlashCoders] Images stay on memory forever? Sounds perfectly normal to me, making something invisble in flash doesnt mean it will unload the content from memory, in fact it doesnt necessarily mean it wont get rendered. Im not sure if this is still the case in fp8 but i know that in previous versions i would also move a clip to -1,-1 to stop the renderer from including it. martin Dimitrios Bendilas wrote: Sorry for posting again, Anyone got any idea? ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
Sounds perfectly normal to me, making something invisble in flash doesnt mean it will unload the content from memory, in fact it doesnt necessarily mean it wont get rendered. Im not sure if this is still the case in fp8 but i know that in previous versions i would also move a clip to -1,-1 to stop the renderer from including it. martin Dimitrios Bendilas wrote: Sorry for posting again, Anyone got any idea? ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [FlashCoders] Images stay on memory forever?
Sorry for posting again,
Anyone got any idea?
You can download an example from:
http://www.zefxis.gr/files/ImageIssue.zip
This is actually very urgent and I haven't been able to find anything so
far.
So if someone has a clue, I'd really appreciate it.
At least can anyone give it a try and tell me I'm not crazy?
Thanks!
Dimitrios
- Original Message -
From: "Dimitrios Bendilas" <[EMAIL PROTECTED]>
To:
Sent: Thursday, August 31, 2006 12:26 PM
Subject: [FlashCoders] Images stay on memory forever?
Hello,
While doind some tests, I ran into something that seems a bit weird to me.
On stage I have two movieclips, "p1" and "p2" and a button, "btn".
Each movieclip has a big bitmap (800x600px).
The following code is on frame 1. These are the only things in my app.
-
var n:Number = 0;
p1._visible = false;
p2._visible = false;
btn.onRelease = function():Void {
_root["p"+n]._visible = false;
n++;
_root["p"+n]._visible = true;
}
-
So when you press the button the first movieclip appears.
When you press it again, it hides the first movieclip (p1)
and shows the second one (p2).
I run the program and watch the memory on the Task Manager:
Program executes: 8MB
Btn pressed once: 10MB
Btn pressed twice: 12MB and it stays there
And yes, if I only show p2 it goes to 10MB as well, so 12MB
is the sum of the two clip's size on memory.
So, I show p1, then hide it, but it doesn't get removed from memory.
Is that how it should behave?
Even if I removeMovieClip() the clip I'm hiding, the memory still doesn't go
down.
It's Flash 8 and the movieclips are not bitmap cached.
Any thoughts?
Thanks,
Dimitrios Bendilas
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
RE: [FlashCoders] Images stay on memory forever?
Hi, I am using MediaPlayBack component for my video files so that it can work on flash player 7. I have around 30 to 35 flv files and I wanted to use only single component. I am trying to change the reference to flv file through url field (URL to the component) of MediaPlayBack component through code, but this is not working. Below is code for same, Name of my MediaPlayBack component is media7_cmp media7_cmp.URL="ASB1006_AlzheimersSwitch.flv"; But component won't accept flv file name through code. Please let me know how do I achieve this. ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
[FlashCoders] Images stay on memory forever?
Hello,
While doind some tests, I ran into something that seems a bit weird to me.
On stage I have two movieclips, "p1" and "p2" and a button, "btn".
Each movieclip has a big bitmap (800x600px).
The following code is on frame 1. These are the only things in my app.
-
var n:Number = 0;
p1._visible = false;
p2._visible = false;
btn.onRelease = function():Void {
_root["p"+n]._visible = false;
n++;
_root["p"+n]._visible = true;
}
-
So when you press the button the first movieclip appears.
When you press it again, it hides the first movieclip (p1)
and shows the second one (p2).
I run the program and watch the memory on the Task Manager:
Program executes: 8MB
Btn pressed once: 10MB
Btn pressed twice: 12MB and it stays there
And yes, if I only show p2 it goes to 10MB as well, so 12MB
is the sum of the two clip's size on memory.
So, I show p1, then hide it, but it doesn't get removed from memory.
Is that how it should behave?
Even if I removeMovieClip() the clip I'm hiding, the memory still doesn't go
down.
It's Flash 8 and the movieclips are not bitmap cached.
Any thoughts?
Thanks,
Dimitrios Bendilas
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
