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
- [Dynapi-Dev] Garbage Collection Raymond Smith
- Re: [Dynapi-Dev] Garbage Collection Richard Bennett
- Re: [Dynapi-Dev] Garbage Collection Raymond Smith
- Re: [Dynapi-Dev] Garbage Collection Raymond Smith
- [Dynapi-Dev] Garbage Collection Raymond Smith
- Re: [Dynapi-Dev] Garbage Collection Robert Rainwater
- Re: [Dynapi-Dev] Garbage Collection Raymond Smith
- [Dynapi-Dev] Garbage collection anders . noras
- RE: [Dynapi-Dev] Garbage collection Scott Andrew LePera
- RE: [Dynapi-Dev] Garbage collection Lasse Lindgard
- RE: [Dynapi-Dev] Garbage collection Lasse Lindg�rd
- RE: [Dynapi-Dev] Garbage collection Ken Ono
