Hi, yeah thanks, it feels it has got the right flow when it sits on the 65 inches screen that is going to run it.
To start with I had it creating and destroying planes but the memory wouldn't get released even after making sure all pointers and all events were deleted from my objects. I guess I could try this approach again in which case what's the best way of deleting my planes from memory? removechild after getting rid of all pointers and listeners is going to be enough? I'm now trying to separate the 3d paper thing from the main app which you can't see in the example. I'm hoping that in this way I can load the away3d element of it from an external swf and then delete it and reload a new one every 20 minutes or so. do you reckon that would get rid completely of the away3d vars and objects? I have also been thinking of reloading the whole application every half an hour or so but it's a last resort kind of thing. thanks for the response so far. Luigi ps I have quite a few apps that are running over 8 hours a day in museums so it can be done in flash, this is the first time I am using away3d and I can see that the leak comes from there. I just wish I understood more of the code of away3d but it just goes over my head ;) On May 10, 2:21 pm, peter gledhill <[email protected]> wrote: > Nice effect, like it. > > I don't have a solution to the problem but I'll just throw my 2 pence > in. > > Bit of a long shot: > You say your reusing your planes, which sounds great idea. But the > fact that something is holding onto the Vector<Number> instances, > perhaps away3d or (tweenMax) is storing the X,Y,Z & rotation > properties for each tween. Maybe you could try not reusing but > creating / destroying a plane each time to see if these properties are > disassociated. > > However even if you fix this memory leek, there will be others. 8 > hours is a long time to run a flash app, maybe you could write a > script to close the programme and re-open it every 30 minutes?
