Ohh no. NS is doing just fine. And NS6 is doing great on the garbage
collection.
It is IE that is the big problem. Most moderatly advanced DynAPI pages that
I have seen leak at least 1 mb pr. reload / click.
I just tested IE6beta and it leaks too.
The big step forward is that the simple DynAPI pages has stopped leaking.
Before 2.5 they leaked around 200kb. Now they don't leak anything that I can
measure. I wonder what the difference is between complex and simple pages ?
Btw. why is DynAPI marked as sourgeforge status 5 (Production/stable). As
long as it leaks I don't think that it should claim more than beta status.
/Lasse
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott Andrew
LePera
Sent: Wednesday, April 18, 2001 7:50 PM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Dev] Garbage collection
I thought the majority of memory leak problems happened in Netscape
instead of IE. Am I mistaken?
Regardless, part of the NS leak problem is probably due to (but not
limited to) two factors:
1. NS doesn't do garbage collection until a new page is loaded (or
reloaded)
2. multiple document.write() statements cause NS to leak oodles of
memory
Unfortunately, without document.write(), Netscape is without a setHTML
method.
scottandrew
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
