Hey Pawel with the recent GC updates, a lot of emphasis has been put on the view holding all reused objects in object pools. With this in mind, i woudl recommend you try to restrict your creation/destruction of obejcts to items other than the view, which *should* have no reason to ever be discarded. if you're still having problems, get in contact and we can analyse your specific use case, as optimised GC is a pretty big function of this next release
cheers! Rob On Wed, Feb 4, 2009 at 1:22 PM, paullaster <[email protected]> wrote: > > You might have to remove all references and delete the model too. > Away3d might be holding on to information in that model so it wont > leave memory. Away3d View3D doesn't have a proper dispose function > and removeChild might not be enough for it clear the model out of > Away3d. I think its known that Away3d has a memory leak in some > areas. Like some of the cameras leak verts. So Away might just be > holding on to itself in memory. I heard through the grapevine that the > new 2.3 build of Away3d addresses a lot of these issues. > > We have started to design our games to navigate through pages so that > we clear the flash memory. -- Rob Bateman Flash Development & Consultancy [email protected] www.infiniteturtles.co.uk www.away3d.com
