I been working with DynAPI 3 for a couple of weeks now. Overall, I'm very
impressed and optimistic about the future of DynAPI.
I'm having trouble with (what I believe is) a memory leak in dynapi.js at
line 106:
f.onunload = function() {
//alert('hi');
for (var i=0;i<o._unloadfn.length;i++) o._unloadfn[i]();
if (o.document) {
o.document._destroy();
o.document = null;
}
};
I'm working on a window widget with quite a few DynLayers and when unload
event triggers, the document unloads before the above function is finished
and I get the following error in IE6:
Error:'this.children[...]' is null or not an object
...at which point I notice that my available system memory has been reduced
by a couple hundred KBytes or so. I get the same error in Netscape 7.1, but
I can get around it by changing the event listener from 'onunload' to
'onbeforeunload'. Alas, this does not fix the problem in IE. Has anyone else
run into this problem? Are there any known workarounds? Thanks in advance
for you help and keep up the good work.
Jeremy Wanamaker
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/[EMAIL PROTECTED]/
