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
11 matches
Mail list logo
