e_baggg,
You're not the only one. We're experiencing very similar problems.
Our app just keeps gobbling memory until the browser crashes. We've had
to resort to calling dispose() explicitly on every mx:Image and bitmap
we ever instantiate, and explicitly calling removeAllChildren() on every
when you need it.
-Alex
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Blake
Barrett
Sent: Tuesday, October 28, 2008 3:09 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Memory issues ... garbage collection only running in
IE (not FF or Safari)
e_baggg
.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Matt Chotin
Sent: 08 December 2006 05:33
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] memory issues / garbage collection?
Actually I forgot, there was a memory leak still found due to an event
Hello,
Maybe in that app, unused BitmapData not disposing. And they eats your
memory.
When you working with images just dispose thas Bitmaps what u no longer
need.
Kenneth Sutherland wrote:
I’ve been playing around with the photoviewer example (from the adobe
site) quite a bit in my
I was having this problem when I built the map component for www.pikeo.com
http://www.pikeo.com/
You have to make sure that all references to an object are gone before it
will get garbage collected.
Once all references to the object are gone it will get collected within 5
seconds usually.
was change a color ;-)
Matt
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Kelly
Sent: Thursday, December 07, 2006 12:20 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] memory issues / garbage collection?
I was having
: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Matt Chotin
Sent: Thursday, December 07, 2006 9:23 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] memory issues / garbage collection?
When we wrote the PhotoViewer there were some memory leaks but I thought
we got them all
7 matches
Mail list logo
