[Dynapi-Dev] The memory leak is about to surrender to my fierceful efforts

[Jordi - IlMaestro - Ministral]

I'm working with IE5.5 under Win98 and using the DynAPI X distribution. So far
here's what I have:

- Creating layers does not leak. The onUnload method goes:

 for(var i in DynObject.all) {
  delete DynObject.all[i]
  DynObject.all[i] = null
 }

- Yep not even the destroy method is required. According to my Task Manager I
don't loose one single byte.

- Creating Event Listeners does not cause leaking.

- Adding event listeners does cause leaking. In fact, it causes a hole the size
of Brazil. I thought that including a EventListener.all array as well and going:

 for(var i=0;i<EventListener.all.length;i++) {
  Methods.destroy(EventListener.all[i])
  delete EventListener.all[i]
  EventListener.all[i] = null
 }

would do the job but, of course, life can't be nice to me. This is the current
status of the issue. I hope to be able to be back tomorrow with a total success,
but I don't know. Just wanted to share what I discovered just in case someone
else wants to try solving this dammed thing without lurking through dynlayer.js
like a madman ( as I have done without any success ).

I'm not sure about what happens with variables. I mean having a myLayer = new
DynLayer will refrain IE from deleting the object because there is one reference
to it ? I don't know.



_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev