All you need is:
function timerHandler(event:TimerEvent):void {
mLoader.unloadAndStop();
startLoad();
trace("timerHandler: " + event);
}
- Original Message -
From: "TS"
To: "'Flash Coders List'"
Sent: Friday, October 02, 2009 9:27 PM
Subject:
lashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Muzak
Sent: Friday, October 02, 2009 5:38 AM
To: Flash Coders List
Subject: Re: [Flashcoders] [MEMORY LEAK]
I'd say, keep the loader instance (instead of creating a new one each time) and
unload
riginal Message -
From: "Gregory Boland"
To: "Flash Coders List"
Sent: Friday, October 02, 2009 5:57 AM
Subject: Re: [Flashcoders] [MEMORY LEAK]
All I can say is that you aren't releasing all of the references to this
material that you are trying to release f
Thanks, T
>
> -Original Message-
> From: flashcoders-boun...@chattyfig.figleaf.com
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Gregory
> Boland
> Sent: Thursday, October 01, 2009 3:39 PM
> To: Flash Coders List
> Subject: Re: [Flashcoders] [MEMORY
: Flash Coders List
Subject: Re: [Flashcoders] [MEMORY LEAK]
TS,
what is the content that you are loading from this external swf every 30,000
milliseconds? It is feasible that what you are loading is causing the
memory of the Flash player to increase?
I never saw where you ready the swf itself for
it in the loader swf?
Thanks, T
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Gregory
Boland
Sent: Thursday, October 01, 2009 3:39 PM
To: Flash Coders List
Subject: Re: [Flashcoders] [MEMORY LEAK]
TS
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Kerry
> Thompson
> Sent: Thursday, October 01, 2009 2:06 PM
> To: 'Flash Coders List'
> Subject: RE: [Flashcoders] [MEMORY LEAK]
>
> Juan Pablo Califano wrote:
>
> > The mere fact that the
> >
PM
To: 'Flash Coders List'
Subject: RE: [Flashcoders] [MEMORY LEAK]
Juan Pablo Califano wrote:
> The mere fact that the
> memory footprint grows doesn't mean there's a leak.
Juan Pablo is correct, and it's important to understand why. (If you already
understand garb
shcoders-boun...@chattyfig.figleaf.com] On Behalf Of Juan Pablo
Califano
Sent: Thursday, October 01, 2009 1:24 PM
To: Flash Coders List
Subject: Re: [Flashcoders] [MEMORY LEAK]
I see. But when you refresh the page, the Flash Player instance is tore
down, so the player's memory is released. When you reload a st
Juan Pablo Califano wrote:
> The mere fact that the
> memory footprint grows doesn't mean there's a leak.
Juan Pablo is correct, and it's important to understand why. (If you already
understand garbage collection, you need read no further, unless you want to
check the accuracy of my description :
refresh it drops
> back to where it was.
>
> Thanks, T
>
> -Original Message-
> From: flashcoders-boun...@chattyfig.figleaf.com
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Juan Pablo
> Califano
> Sent: Thursday, October 01, 2009 6:35 AM
> To:
f Ian Thomas
Sent: Thursday, October 01, 2009 2:18 AM
To: Flash Coders List
Subject: Re: [Flashcoders] [MEMORY LEAK]
Just out of interest - why are you recreating the Loader() and
re-adding the listeners each time? It should work if you just create
the Loader once, add the listeners once - then every
refresh it drops
back to where it was.
Thanks, T
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Juan Pablo
Califano
Sent: Thursday, October 01, 2009 6:35 AM
To: Flash Coders List
Subject: Re: [Flashcoders] [M
nly if the XML file has
nodes with an attribute of id.
--- On Thu, 10/1/09, Ian Thomas wrote:
From: Ian Thomas
Subject: Re: [Flashcoders] [MEMORY LEAK]
To: "Flash Coders List"
Date: Thursday, October 1, 2009, 4:17 AM
Just out of interest - why are you recreating the Loader() and
re-
Every time it reloads
however, I watch firefox take away memory consistently and when I refresh
that page memory use drops back to normal.
>>>
First and most important, are you sure it's leak? The fact that Firefox (not
even the player itself) doesn't release memory right away doesn't mean
.figleaf.com
> [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Chris Foster
> Sent: Wednesday, September 30, 2009 7:08 PM
> To: Flash Coders List
> Subject: RE: [Flashcoders] [MEMORY LEAK]
>
> Hi T,
>
> No solution here, but this might relate to your curren
Try removing any listeners associated with that swf before unloading
it. It's possible the remaining listeners are still listening. Someone
may be able to verify this more than I though.
HTH
Karl
Sent from losPhone
On Sep 30, 2009, at 7:53 PM, "TS" wrote:
Hello, this issue is killing me.
esday, September 30, 2009 7:08 PM
To: Flash Coders List
Subject: RE: [Flashcoders] [MEMORY LEAK]
Hi T,
No solution here, but this might relate to your current problem:
http://www.gskinner.com/blog/archives/2008/04/failure_to_unlo.html
C:
-Original Message-
From: flashcoders
Hi T,
No solution here, but this might relate to your current problem:
http://www.gskinner.com/blog/archives/2008/04/failure_to_unlo.html
C:
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of TS
Sent: Thur
Are you using Bitmaps and/or BitmapData?
In that case try doing bitmapData.dispose() or
bitmap.bitmapData.dispose() when clearing an image
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom
Huynen
Sent: 03 September 2007 22:09
To: flashcoders@chattyfig.fi
you should read gskinners' reasearch on this, it's a 3 part story, pretty
interesting.
http://www.gskinner.com/blog/archives/2006/06/as3_resource_ma.html
part 3 describes a way to force the gc to actually execute, for testing
purposes.
-Meinte
On 9/6/06, Michael Trim <[EMAIL PROTECTED]> wrote:
http://www.iarsn.com/taskinfo.html
On 3/15/06, Darren Cook <[EMAIL PROTECTED]> wrote:
> > There was also a utility that someone on the team found that would
> > force it to release the memory. But it was Windows only, and we had to
> > support Mac so we ended up taking it out.
>
> Do you have a li
> There was also a utility that someone on the team found that would
> force it to release the memory. But it was Windows only, and we had to
> support Mac so we ended up taking it out.
Do you have a link or a name for that utility (I only need to support
windows in the current project so that may
> This is the same thing that I discovered on a project last
> year. We even discussed the issue with Macromedia and they
> basically told us that the player was not intended to run for
> long periods of time.
You're kidding me? They won't support embedding the activeX control, and
then they
Darren Cook
> Sent: Tuesday, March 14, 2006 2:42 AM
> To: Flashcoders mailing list
> Subject: Re: [Flashcoders] Memory leak in Flash projector
>
> On Feb 25th 2006 Andreas Rønning wrote:
> > This is very serious. The majority of my work is kiosk apps.
> > Any more detail
arch 2006 23:01
> To: 'Flashcoders mailing list'
> Subject: RE: [Flashcoders] Memory leak in Flash projector
>
> I had similar issues and solved it by minimizing/restoring
> the App via a third party wrapper (SWF Studio in my case) in
> an Interval.
> It seems that by d
: Flashcoders mailing list
Subject: Re: [Flashcoders] Memory leak in Flash projector
On Feb 25th 2006 Andreas Rønning wrote:
> This is very serious. The majority of my work is kiosk apps.
> Any more details on this, official Macromedia stance on it? Future fixes?
Does anyone have more infor
FYI, I can't speak specifically to either root cause or eventual effect/fix,
but this entire thread has been routed to the Player team for triage and
consideration (as will any subsequent suggestions/comments that follow
fhere). Thanks for bringing it to our attention!
-Scott
scott fegette
adobe
On Feb 25th 2006 Andreas Rønning wrote:
> This is very serious. The majority of my work is kiosk apps.
> Any more details on this, official Macromedia stance on it? Future fixes?
Does anyone have more information on this? For instance what kind of
features or media types or actionscript are causin
Well, just today i filled 3 bugs reports on memory leaks and things that
don´t get drawn correctly, all with test cases.
v8 also has problems with the new ExternalInterface under IE, if the
tag is inside a form.
Hope someone at Adobe fix all of this...
On Fri, 24 Feb 2006 16:19:03 -0300, An
This is very serious. The majority of my work is kiosk apps.
Any more details on this, official Macromedia stance on it? Future fixes?
- Andreas
Marcelo Volmaro wrote:
Well, unless you used a lot of the new FX, i recommend you going back
to the v7 player. The v8 has a lot of errors/memory leaks
Well, unless you used a lot of the new FX, i recommend you going back to
the v7 player. The v8 has a lot of errors/memory leaks, mostly of them
related to the new bitmap engine.
I recently had to change a lot of code that takes advantage of the new
system to the old one, because a lot of th
32 matches
Mail list logo
