Hi, You are using the latest release, right? There were memory leaks in previous versions (as this.fame was not being set to null) , I have not had this problem recently.
If so, please submit it as a bug, but also supply a little test-code to replicate this problem, that we can put in the /tests directory, if you can. Your solution does seem logical though. cheers, Richard. ----- Original Message ----- From: "Phillips, Stephen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 16, 2001 11:57 AM Subject: [Dynapi-Dev] Memory leak > Immediate apologies if this has been discussed before, but I've searched > both the docs and the list archives..... > > We have a serious memory leak when using DynApi - this has been tracked to > DynObject.all retaining a reference to every created DynObject, even though > we do want them deleted (by calling "deleteAllChildren()" on our top level > container layer). > > The constructor for DynObject calls "setID()", which in turn adds iteself > into DynObject.all. It looks like the finalizer for the class is the > "del()" function - however, there is no removal of the object from > DynObject.all. > > A quick test shows that sticking: > > delete DynObject.all[this.id] > > at the bottom of "del()", solves the problem with no apparent side-effects. > Is this a real bug, or is there something I've missed which means the object > must be kept? > > If the former then I'll raise it as a bug. If the latter, then we have a > way of cleaning up our DynLayer subclasses automatically, but not when we > use built in sub-classes (e.g. Button). We could change our local dynapi > files, but this is then a maintenance burden. > > Cheers, > Steve. > > > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/[email protected]/ > _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/[email protected]/
